![]() |
|
|
|
|
Issue Type:
|
![Story]() Story
|
|
Affects Versions:
|
5.0, 4.5 |
|
Assignee:
|
Unassigned |
|
Created:
|
31/Oct/13 4:06 PM
|
|
Description:
|
A decision was made in the architecture meeting on October 31, 2013 with at least Philipp, Jan and Daniel present that same name siblings in JCR will officially not be supported in Magnolia. As i understand it, in many ways same name siblings are already not supported in many specific cases. And now we can simplify the system by enforcing this policy.
(Note that this was raised by http://jira.magnolia-cms.com/browse/MAGNOLIA-5311 and its related support ticket.)
Tasks:
- change the default node type definition to not allow same name siblings in a first place and
- distribute script to update existing installations with new node type definition
- add install condition to check that same name siblings are not allowed
|
|
Fix Versions:
|
4.5.14, 5.2 |
|
Project:
|
Magnolia
|
|
Labels:
|
jcr
|
|
Priority:
|
![Neutral]() Neutral
|
|
Reporter:
|
Christopher Zimmermann
|
|
Security Level:
|
Public |
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
