[MGNLUI-6730] Importing / Exporting same item at root path creates inconsistency data Created: 07/Jun/21  Updated: 22/Jun/21  Resolved: 17/Jun/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.9
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-7005 It's possible to create same name sib... Closed
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

 Description   

Steps to reproduce

  1.  Go to pages app at our demo
  2.  Export /sportstation node
  3. Import it
  4. Check the site sport station is duplicated

Expected results

The following error is thrown Caused by: javax.jcr.ItemExistsException: This node already exists: /sportstation

Actual results

The node is imported duplicating the existing one

Workaround

N/A

Development notes

This behavior also happens on Contacts and Assets app. But it only applies on the root level of the workspaces, if you try to export / import a child node, e.g, /sportstation/about, then the expected exception (node already exists) is thrown:

Caused by: javax.jcr.ItemExistsException: This node already exists: /sportstation/about

Generated at Mon Feb 12 09:39:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.