[MGNLXAA-78] Versioning fails if there's a new subnode with same name as existing one but different UUID Created: 02/Jul/14  Updated: 08/Aug/14  Resolved: 07/Jul/14

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-5821 Publishing fails on versioning of new... 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
Date of First Response:

 Comments   
Comment by Daniel Lipp [ 02/Jul/14 ]

As CopyUtil in xa is very similar to the one from core (except that it's still based on Content-API) the fix should be almost identical to the one applied in MAGNOLIA-5821.

Comment by Roman Kovařík [ 07/Jul/14 ]

Only test added since I wasn't able to reproduce the issue locally or on a live instance.
For QA: Note that you need to follow the steps mentioned in MAGNOLIA-5821 + launch publishing! to reach info.magnolia.module.exchangetransactional.CopyUtil.

Comment by Daniel Lipp [ 07/Jul/14 ]

Because of MAGNOLIA-5821 we thought we'd have the same issue in XA module as well. Closing now as it couldn't be reproduced in XA.

Generated at Mon Feb 12 11:06:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.