[MGNLDATA-162] CLONE -Subtype dialog reload incorrectly after validation error. Created: 11/Dec/12  Updated: 11/Feb/13  Resolved: 13/Dec/12

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.6.3
Fix Version/s: 2.0

Type: Bug Priority: Critical
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLDATA-127 Subtype dialog reload incorrectly aft... Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty

 Description   

Steps to reproduce the problem:

  • Create a new type in Data module (I will reference it as "myType")
  • Create a subtype for the new type (I will reference it as "mySubType")
  • Define a simple dialog for myType
  • Define another dialog for mySubType, adding a new edit control
  • Mark the edit control of the subtype as required
  • Go to the tree and create a new instance of myType, and save it
  • Select the instance and click on "new", the dialog of mySubType will show
  • Try to save the empty dialog

The validation stop the saving process, and the error message for the required field is shown correctly. But the dialog behind now is the myType one, and not the mySubType I would expect.
Saving that dialog may cause a real mess in some cases... You will have then a node of myType under another node of myType even if your configuration would not allow it, the user is expecting some data to edit at that level but opening the faulty node will show another dialog (myType instead of mySubType), and obviously xpath queries may have unexpected results.



 Comments   
Comment by Jaroslav Simak [ 12/Dec/12 ]

Port of MGNLDATA-127 to master.

Generated at Mon Feb 12 05:11:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.