[MGNLFE-217] Greenbars not rendering on Headless Acelerator new pages using Angular 1.2.1 Created: 13/Jun/22  Updated: 06/Apr/23  Resolved: 04/Jul/22

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3.0

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Phong Le Quoc
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 4.75h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLFE-218 Regression Angular editor not creatin... Closed
causality
dependency
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support
Sprint: DevX 13
Story Points: 3
Team: Services

 Description   

Steps to reproduce:

1 - Create a jumpstart project using Headless Acelerator and selecting Angular for the project.

2 - Creating a subpage to the default page by default.

Expected:

Green bars are rendered and allow you to insert components.

Outcome:

Page is blank and doesn't allow you to edit nor add components.

Workaround & notes:

Setting spaExtended as the renderType either on package.json or individually for each template, allows you to edit and insert components.

Also, creating a page or rendering it using spaExtended as renderType, allows you to edit it regardless of the renderType set afterwards (can switch to spa as renderType and it will work).



 Comments   
Comment by Christopher Zimmermann [ 29/Jun/22 ]

This ticket will be resolved by https://jira.magnolia-cms.com/browse/HA-122

Comment by Phong Le Quoc [ 04/Jul/22 ]

This ticket will be resolved by https://jira.magnolia-cms.com/browse/MGNLFE-218 also.

Comment by Phong Le Quoc [ 04/Jul/22 ]

It is the same root cause with MGNLFE-218

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