-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
Currently the XML import will allow the XML to contain duplicate node names and import them. Since Magnolia doesn't support duplicate node names in a lot of places (e.g. versioning and activation), this can lead to serious problems. This can happen with XML generated outside of Magnola or hand-written/modified XML.
The XML import logic should either reject the import or rename nodes appropriately while importing.
Acceptance criteria