[PAGES-491] Make sure that page/component creation actions are able to provision required area node surrounding Created: 27/Aug/21  Updated: 02/Nov/21  Resolved: 01/Oct/21

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-6890 Make sure succession calls to JcrNode... Closed
is depended upon by MGNLFE-110 Handle missing area nodes in SPA Closed
is depended upon by MGNLFE-117 Create missing area nodes on client-s... Closed
supersession
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: External SPA
Sprint: HL & LD 37, HL & LD 38
Story Points: 3

 Description   

Current component/page creation flow:

  • multi-step: first we select template/position which is not meant to be yet stored in JCR (we may cancel the action); we store this info in a transient bean and carry over to next step (properties dialog) and only then save everything to JCR.
  • where do area nodes need to appear?
    • currently parent node reference is already mixed in the transient bean at the component creation time (see the PAGES-470 re: why)
    • if we are talking about none existent area nodes, maybe we can defer the node creation to the very end.

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