[ http://jira.magnolia.info/browse/MAGNOLIA-1819?page=all ]
Vivian Steller resolved MAGNOLIA-1819.
--------------------------------------
Resolution: Fixed
This fix could possibly break some cms:out tags as both use BaseContentTag to
resolve the firstMatchingNode;
anyway with this fix both tags work as one would expected (before cms:out
expected node to be null if contentNodeName was empty but
contentNodeCollectionName was provided; now we return the contentNodeCollection
instead of null).
> cms:ifEmpty does not behave as expected for contentNodeCollectionName
> ---------------------------------------------------------------------
>
> Key: MAGNOLIA-1819
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1819
> Project: Magnolia
> Issue Type: Bug
> Components: taglibs
> Affects Versions: 3.1 M3
> Reporter: Vivian Steller
> Assigned To: Vivian Steller
> Fix For: 3.1
>
>
> <cms:ifEmpty contentNodeCollectionName="someName" /> does not behave as
> expected, once there is something in this contentNodeCollectionName it still
> says that its empty (always returns true).
> Note that this tag is used at the top level and is not contained within
> container loop.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
