[PAGES-151] Same name sibling created when importing xml file Created: 12/Dec/17 Updated: 12/Dec/17 Resolved: 12/Dec/17 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 5.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Julie Legendre | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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: | |||||||||
| Description |
|
Same name siblings can be imported with dire consequences. To reproduce:
>>> see screenshot1, screenshot2 and screenshot3 Something similar happens in Contacts app too. |
| Comments |
| Comment by Bradley Andersen [ 12/Dec/17 ] |
|
I can confirm this behavior on 5.5.7. Create a page, export it as XML, then re-import it at the same level. See attached screen shots. Caveat: of course the underlying JCR implementation does not give SNS - they are named thing[1] and thing[2]. But, in the UI they have the same name, so:
|