[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23369#action_23369
]
Hudson CI server commented on MAGNOLIA-2801:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#909|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/909/]
Do not store temporary nodes directly under activated node as this might
not support such child node types.
> Node properties update during activation is too restrictive
> -----------------------------------------------------------
>
> Key: MAGNOLIA-2801
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2801
> Project: Magnolia
> Issue Type: Improvement
> Components: activation
> Affects Versions: 4.0.1, 3.6.5, 4.1
> Reporter: Jan Haderka
> Assignee: Jan Haderka
> Fix For: 4.1.1
>
>
> Currently to update the properties of existing node on re-activation, the
> temporary subnode of CONTENT_NODE type is created to hold updated properties.
> Therefore any content has to allow for such children. This is too restrictive
> for some content types(e.g. {{mgnl:forum}}, and possibly custom data module
> types as well) and is unnecessary.
--
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]>
----------------------------------------------------------------
