Re: Overriding work around

Andrew C. Altepeter wrote:
>>>AFAIK, this behaviour has been there forever
>>
>>By which I don't mean to say we shouldn't change it!
>>
>>I just didn't regard it as a bug, since it was the intended behaviour all a
>>long. We now might have other requirements of course.
> 
> I don't necessarily think it's a bug either, but in our environment we
> have always changed changed the acquisition behavior, removing the '.aq_explicit'.

How's the behaviour of 'override.html' different from 'content.html' if you 
remove the explicit acquisistion?

Content.html was meant to set the rendering of content for a complete subtree, 
where the override.html was meant to set the rendering for the context it is in 
only.



regards,
jw

-- 
Jan-Wijbrand Kolman
[email protected]