-
Bug
-
Resolution: Fixed
-
Major
-
4.5.11, 5.0.4
-
None
-
-
Empty show more show less
-
4.5.13
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.
- is causing
-
MAGNOLIA-5433 As a developer it's clear that I cannot use same name siblings in Magnolia
- Closed
- is related to
-
MAGNOLIA-613 Import of XML Data makes problems
- Closed
-
MAGNOLIA-5444 CLONE: XML import should prevent duplicate node names
- Closed