[MAGNOLIA-5540] Propagate the same name sibling restriction during migration from M4.5 to M5 Created: 11/Dec/13  Updated: 13/Dec/13  Resolved: 13/Dec/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.2
Fix Version/s: 5.2.1

Type: Bug Priority: Critical
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-2518 Do not migrate acl if they already exist Closed
relation
is related to MAGNOLIA-5434 Default node type definition should n... Closed
is related to MGNLSTK-1320 Do not create stkPURPasswordChangeFor... 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:

 Description   

The nodeType definition introduce a new restriction for child nodes. Same name sibling are no more supported. This new restriction is not included in the migration process.



 Comments   
Comment by Roman Kovařík [ 11/Dec/13 ]

Create tickets in related modules and link commits there because some commit under this tickets belong to another modules.

Comment by Roman Kovařík [ 11/Dec/13 ]
Comment by Eric Hechinger [ 13/Dec/13 ]

RegistryDialogMigrationTask is replaced by DialogMigrationTask.

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