Hi, the following ticket introduced a new policy for rendering areas:
http://jira.magnolia-cms.com/browse/MAGNOLIA-5029 If no component in the area exists, the whole rendering of the area script is skipped. This breaks our existing applications which worked fine since we started using 4.5. We don't use STK, but built our frontends from scratch. We use <cms:area> in our templates which includes the area script which decides what to do when no component is present (e.g. rendering a set of different components (not always inherited) or meaningful placeholders). But with 4.5.9 the whole area script isn't called anymore. My question: is this new behaviour fixed for the upcoming versions so we have to fix our applications? Or is this change going to be reverted (at least to be configurable) in the future? Cheers, Maik -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=35028cb5-ff25-4217-87eb-d7d9556473f0 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
