Re: Overriding work around

Hey,

After a chat with JW here, I think I understand now where I went wrong, 
and what you want. Not yet how to solve the problem, but it's an 
important step in the direction. :)

I was confusing the behavior of 'override.html' with that of 
'content.html', which is why I was saying override should affect 
documents. That's not true; disregard all that -- that's the behavior of 
content.html.

Override.html indeed only affects folders, and the misbehavior is that 
when you go to its /index directly, you don't see it. A patch along the 
lines of Benno makes sense to fix it, and I don't see drawbacks.

Sorry for having us all wander up the wrong trail!

Regards,

Martijn