[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-2704:
----------------------------------
Fix Version/s: (was: 4.1 RC1)
(was: 3.6.x)
(was: 4.0.2)
Unfortunately solution for this issue have been conflicting with solution for
MAGNOLIA-2771 which was a blocker for release 4.1. Solution to this issue
(while keeping changes necessary for MAGNOLIA-2771) will be revisited after the
release.
> activation: support activation of same name siblings
> ----------------------------------------------------
>
> Key: MAGNOLIA-2704
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2704
> Project: Magnolia
> Issue Type: Bug
> Components: activation
> Affects Versions: 4.0.1
> Environment: OpenJDK 1.6.0 on CentOS 5.3 64bit with ext3 filesystem,
> Magnolia OnAir 4.0.1
> Reporter: Manfred Stock
> Assignee: Jan Haderka
> Attachments: author-data.rtsi.proxyObjects.2009.04.02.Test-05.xml,
> public-data.rtsi.proxyObjects.2009.04.02.Test-05.xml
>
>
> In situation where it is possible that two same name siblings exist, during
> activation of these nodes, the {{MetaData}} nodes get mixed up between the
> two nodes (i.e. it seems that the 'first' node gets the content of the
> 'second' node's {{MetaData}} node).
> It is possible to reproduce this by importing the attached
> {{author-data.rtsi.proxyObjects.2009.04.02.Test-05.xml}} into the {{data}}
> workspace, and then trying to activate it. The data in the author instance
> will be ok, but the data in the public instance will be mixed up, about as in
> the above example.
--
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]>
----------------------------------------------------------------
