[PAGES-1128] Component Autogeneration should work in SPA Editor Created: 21/Sep/20  Updated: 14/Jun/23  Resolved: 23/May/23

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

Type: Bug Priority: Major
Reporter: Chris Jennings Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 1d 7.25h Time Spent: 1d 7.25h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLFE-182 Discovery - Component Autogeneration ... Closed
Problem/Incident
Relates
relates to PAGES-1153 Component Inheritance with Visual SPA... Closed
relates to PAGES-1162 DOC: Component autogeneration and inh... Closed
relates to MGNLREST-732 Tune default configuration of jcrPage... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-1129 Implementation Sub-task Completed Oanh Thai Hoang  
PAGES-1130 Review Sub-task Completed Javier Benito  
PAGES-1131 piQA Sub-task Completed Javier Benito  
PAGES-1132 QA Sub-task Completed Phong Le Quoc  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Support
Sprint: DevX 37, DevX 38
Story Points: 3
Team: DeveloperX
Work Started:
Approved:
Yes

 Description   

Magnolia's component autogeneration functionality allows page areas to be populated with required components. See: https://documentation.magnolia-cms.com/display/DOCS62/Component+autogeneration

In an FTL-rendered site the configured components are created by AreaElement but nothing happens in an MGNLFE site.

For Discovery phase:

  • Estimation for amount of time to implement.
  • Investigate possible approaches. 

 



 Comments   
Comment by Sebastian Haftmann [ 19/Oct/21 ]

Is there a rough ETA for auto gen support in SPA editor? Our migration to 6.2-project relies heavily on auto gen and depending on the ETA we would consider different workaround-options. Thank you!

Comment by Christopher Zimmermann [ 20/Oct/21 ]

Hi Sebastian, I cannot give a rough ETA. As things stand, I wouldn't expect it in the next 6 months.

Comment by Mykola [ 29/Sep/22 ]

maybe https://docs.magnolia-cms.com/headless/api/spa-templating.html#_spa_template_definitions_endpoint would help?
if we have definition then it would be matter of:
1) request page data
2) if certain area doesn't have content -> request template definition
3) if area in def have autoGeneration field, then pass content from it
it would be great to implement it on spa editor side

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