As a developer it's clear that I cannot use same name siblings in Magnolia (MAGNOLIA-5433)

[MAGNOLIA-5434] Default node type definition should not allow same-name siblings Created: 31/Oct/13  Updated: 11/Dec/13  Resolved: 08/Nov/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.1.1
Fix Version/s: 5.2

Type: Sub-task Priority: Critical
Reporter: Christopher Zimmermann Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLDATA-224 VersionHandler test fails due to forb... Closed
relation
is related to MAGNOLIA-5463 Change implementation of copyInSessio... Closed
is related to MAGNOLIA-5540 Propagate the same name sibling restr... Closed
is related to MGNLUI-2358 Adapt tests as same-name siblings are... Closed
is related to MGNLUI-2321 Save actions do not take a node type ... Closed
Template:
Release notes required:
Yes
Date of First Response:
Sprint: 5.2-rc2

 Description   

Because same name siblings are no longer supported in Magnolia.



 Comments   
Comment by Daniel Lipp [ 06/Nov/13 ]

Reverted the commit to master: The fix itself is consistent within m_main but causes failures in tests of other modules (e.g. MGNLUI-2358) - also the bundle build is failing now. Needs to be thoroughly tested before it can be re-applied to master.

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