Hi,
in Magnolia 4.5 you can configure your areas to be of type 'single' or 'list'
(or 'none'). First of all I don't think (but maybe I missed this) it is not so
clearly documented that this choice also determines how you need to retrieve
your components in your custom area (n.b. you don't always need a custom area).
For single areas you need to do (JSP syntax):
[code]<cms:component content="${component}"/>[/code]
For list areas you need to do:
[code] <c:forEach items="${components}" var="component">
<cms:component content="${component}" />
</c:forEach>[/code]
That is fair enough. But I notice some strange behavior with single areas. On
some of our pages that have multiple custom single areas with JSP code as above
I see that some areas fail to render their own components but instead seem to
render the components of other areas on the page? Very strange. If I change all
areas to list areas instead of single the problem dissappears. Also, I do not
have the problem with 'default' single areas (i.e. areas that do not have a
corresponding JSP/FTL).
I wonder: is there something special about single areas that I should know
about?
cheers,
Edgar
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=9e5094f5-8f8e-48f8-b792-ef1f20a00916
----------------------------------------------------------------
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]>
----------------------------------------------------------------
