[MGNLUI-2321] Save actions do not take a node type structure into account. Created: 25/Oct/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.1.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-5434 Default node type definition should n... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Daniel Lipp [ 05/Nov/13 ]

a) should no longer be valid, once MAGNOLIA-5434 is fixed

Generated at Mon Feb 12 08:55:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.