-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
5.1.1
-
None
-
None
When the custom-defined node type defines an auto-generated sub-node we end up with bad consequences when creating entries with detail sub-app:
a) two such sub-nodes after performing save - in case same-name siblings are allowed;
b) node exists already exception - in other case.
Acceptance criteria
- is related to
-
MAGNOLIA-5434 Default node type definition should not allow same-name siblings
-
- Closed
-
