[MAGNOLIA-5441] CLONE - XML import should prevent duplicate node names Created: 01/Nov/13  Updated: 27/Apr/18  Resolved: 27/Apr/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.13, 5.1.2, 5.2

Type: Bug Priority: Major
Reporter: Cheng Hu Assignee: Peili Liang
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support

 Description   

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.



 Comments   
Comment by Antti Hietala [ 27/Apr/18 ]

Done inĀ MAGNOLIA-5311 for 4.5 and in MAGNOLIA-5433 for 5.x.

Generated at Mon Feb 12 04:05:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.