As a developer it's clear that I cannot use same name siblings in Magnolia
(MAGNOLIA-5433)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.5, 5.0 |
| Fix Version/s: | 5.2 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Date of First Response: | |
| Sprint: | 5.2-rc2 |
| Description |
|
The new node type definition does not allow same-name siblings. We have to provide migration task that has to be used in version handler.
|
| Comments |
| Comment by Jozef Chocholacek [ 07/Nov/13 ] |
|
Scripts from Zdenek, siblings.groovy is for the 4.5+ API, siblings44.groovy for the older one (4.4). |
| Comment by Eric Hechinger [ 12/Nov/13 ] |
|
commit made in |
| Comment by Eric Hechinger [ 14/Nov/13 ] |
|
IdentifySameNameSiblingNodesTask#performQuery() commented out code should be removed |
| Comment by Eric Hechinger [ 14/Nov/13 ] |
|
Update task documentation: |