[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21494#action_21494
]
Hudson CI server commented on MAGNOLIA-2642:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#716|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/716/]
: use current content of the aggrigation state to save the local content
node
> aggregation state: use current content property consistently
> ------------------------------------------------------------
>
> Key: MAGNOLIA-2642
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2642
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 4.0 RC3
> Reporter: Philipp Bracher
> Assignee: Philipp Bracher
> Priority: Blocker
> Fix For: 4.0 RC4
>
>
> We have cleaned the rendering API but finally we have not change the fact
> that the so called local content node is not set on the aggregation state.
> In magnolia 4.0 we support officially only two global attributes (in the
> aggregation state)
> - main content (the content we start rendering with, entry point)
> - current content (the currently rendered content, mostly the paragraph node)
> all other attributes (used in the tags or Resource class) are deprecated and
> should not be used.
--
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]>
----------------------------------------------------------------
