Aborting page properties dialog leaves traces in workspace (PAGES-271)

[PAGES-291] Committing page properties after aborting it previously creates incorrect hierarchy Created: 20/Apr/20  Updated: 29/Apr/20  Resolved: 29/Apr/20

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Rishab Dhar Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Sprint: UI Framework 21, UI Framework 22, TE 1, TE 2

 Description   

Steps to reproduce

  1. Open pages app and click Add page action
  2. Fill page name a and select a page template (with a page properties dialog)
  3. Click next to open page properties dialog
  4. Click cancel to close the dialog
  5. Repeat Steps 1-3 (but set page name as b), and then click Commit.

Expected results

 
Page b to be created at root level in tree view 

Actual results

Page a/b is instead created

Development notes

This issue stems from ValueContext still containing the Wrapped Page Node in step 5 to maintain page state across requests. As a result of which the new page created incorrectly uses the page from the aborted create properties dialog as parent.



 Comments   
Comment by Rishab Dhar [ 29/Apr/20 ]

The new solution in PAGES-271 does not cause this issue anymore.

Generated at Mon Feb 12 06:17:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.