[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss reopened MAGNOLIA-2704:
---------------------------------------
I am reopening the issue because this has unwanted side effects. For now (4.1)
magnolia activation will just not support activation of same name siblings.
Magnolia as such is dependent on having unique names (urls, ..) in several
places.
Following I list some scenarios which brought me to that decision. In all this
situation the logical same path on author and public actually have a different
uuid and would become same name siblings after an activation while a user
expects that an activation leads to overwriting that node.
1) installation task / update tasks
- creates a node structure and the nodes get the uuid just in time
2) STK: templates, resources, images in dms
- the are installed by tasks but not by bootstrap files
- same path has different uuid on author and public
3) root node of data types in the data module
- they are also created and not bootstrapped
4) import of data (not jcr import)
- like fetching products from a service and adding them to the data module
> Activation of two nodes with the same name results in mixed-up metadata node
> in the subscriber
> ----------------------------------------------------------------------------------------------
>
> 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
> Fix For: 3.6.x, 4.0.2, 4.1 RC1
>
> 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]>
----------------------------------------------------------------
