[PAGES-192] Create/save parent area node upon saving its first component Created: 19/Sep/19  Updated: 23/Aug/22

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

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PAGES-211 Investigate: Extract GWT page-editor ... Closed
supersession
supersedes PAGES-175 Create area nodes when editing a SPA 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)
Release notes required:
Yes
Date of First Response:
Epic Link: SPA Editor Backlog
Story Points: 5
Team: AuthorX

 Description   

User story:

As a content author I need the page editor to create new area nodes when I create a new page or when I place a component which has areas, so that I can properly use the Page Editor

Acceptance criteria:

  • Unless a strategy like "createAreaNode=false" is used, an mgnl:area JCR node is created for the area when a new component is added to it.

For additional rationale and information: https://documentation.magnolia-cms.com/display/DOCS61/SPA+genesis#SPAgenesis-WhyandwhenshouldAreaNodesbecreated

 



 Comments   
Comment by Mikaël Geljić [ 19/Nov/19 ]

Indeed this got covered in SPA renderer so far; this is no longer critical. Will only become relevant again if/when we drop the SPA renderer in favor of the standalone page-editor (PAGES-211).

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