[MAGNOLIA-7005] It's possible to create same name siblings (only under root node) Created: 07/Apr/17 Updated: 03/Mar/23 Resolved: 16/Dec/21 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.0, 6.2 |
| Fix Version/s: | 6.2.15 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Thuy To |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 6d 7.5h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Global Maintenance 2, Global Maintenance 3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
This is due to a bug in jackrabbit which allows same name sibling at root even though same name siblings are disabled by repo config. |
| Comments |
| Comment by Thuy To [ 30/Nov/21 ] |
|
Hi rkovarik , Please help me verify if i'm wrong. The same name sibling issue is occurring when importing a page on Page app. Could we disable the import button on UI to prevent the same name sibling issue instead of fixing on addNode action?
Thanks :bow: |
| Comment by Roman Kovařík [ 30/Nov/21 ] |
|
Hey thuy.to, that would workaround the problem only for UI, but the problem would remain for adding node/import by code. I will check where the fix could be and update this comment with a suggested code change. patch.patch
Roman
|
| Comment by Thuy To [ 30/Nov/21 ] |
|
Thank you very much rkovarik . I'll apply and test it. 🙇♀️ |
| Comment by Thuy To [ 10/Dec/21 ] |
|
Hi rkovarik , Importing a page with the same name siblings will throw an error after this ticket is done. Do we have the follow up ticket to handle this error on UI? |
| Comment by Thuy To [ 16/Dec/21 ] |
|
For release notes: When importing a page with the same name siblings, it throws the error in both log and browser.
Created the follow-up ticket to handle this error on UI: https://jira.magnolia-cms.com/browse/MGNLUI-6992
|