Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
6.0, 6.2
-
None
-
-
Empty show more show less
-
Yes
-
Global Maintenance 2, Global Maintenance 3
-
3
Description
MAGNOLIA-6893 fixed this problem for move actions but the same problem is there for:
- adding node by code (Node#addNode action)
- import (hopefully will be fixed by fixing addNode, to be checked)
MAGNOLIA-6893 already introduced a session wrapper, we just need to add a node wrapper.
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.
Checklists
Attachments
Issue Links
- causes
-
MAGNOLIA-8309 Missing "Add" actions in the "Security" app -> "Users" tab after clean install
-
- Closed
-
-
PAGES-470 Concurrent creation of pages/components works only for the first user
-
- Closed
-
- duplicates
-
PAGES-151 Same name sibling created when importing xml file
-
- Closed
-
-
MGNLUI-2717 With drag-and-drop before and after a node you can create same name siblings
-
- Closed
-
- is causing
-
PAGES-424 Wrong page is marked as deleted
-
- Closed
-
- is duplicated by
-
MGNLUI-6730 Importing / Exporting same item at root path creates inconsistency data
-
- Closed
-
- is related to
-
MGNLUI-6992 Handle an error on UI when importing a page with the same name siblings
-
- Open
-
- relates to
-
MAGNOLIA-6893 Move action doesn't check for possible 'same name' siblings
-
- Closed
-
-
MAGNOLIA-8812 It's possible to import same name siblings from XML (only under root node)
-
- Open
-