[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss resolved MAGNOLIA-2144.
---------------------------------------
Fix Version/s: 4.3
Resolution: Fixed
All returned children are now wrapped too.
> Modify NodeMapWrapper to handle Content children
> ------------------------------------------------
>
> Key: MAGNOLIA-2144
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2144
> Project: Magnolia
> Issue Type: Improvement
> Components: taglibs
> Affects Versions: 3.5.4
> Reporter: Dallas Vaughan
> Assignee: Fabrizio Giustina
> Priority: Minor
> Fix For: 4.3
>
>
> Modify the class info.magnolia.cms.taglibs.SetNode$NodeMapWrapper to handle
> EL expressions such as "${content.childContent}" so that usages such as...
> <cms:setNode var="content" />
> <cms:setNode var="myContent" contentNode="${content.myChildContent}">
> ...can set a child node to a variable. Currently, only "built-in" properties
> (such as title) and child NodeData objects are supported. This would also
> be helpful in other tags that are based on the BaseContentTag (i.e., any tag
> that can has a "contentNode" attribute).
> It *should* be easy to implement: in addition to handling child NodeData
> nodes when calling "containsKey" and "get", handle child Content nodes as
> well. Of course, the "size()" method currently returns the size of the
> NodeDataCollection, so I don't know how to handle that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
