[PAGES-503] Template annotations endpoint too strict in terms of JCR data and LM yaml definitions Created: 06/Jul/21  Updated: 02/Nov/21  Resolved: 21/Sep/21

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

Type: Bug Priority: Major
Reporter: Bartosz Staryga Assignee: Canh Nguyen
Resolution: Done Votes: 0
Labels: VN-Implementation, VN-Testing, headless-team-support
Remaining Estimate: 0d
Time Spent: 2d 7.5h
Original Estimate: Not Specified

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
Epic Link: SPA Editor Backlog
Sprint: HL & LD 37
Story Points: 3

 Description   

Steps to reproduce

  1.  Create page with https://git.magnolia-cms.com/projects/MODULES/repos/frontend-helpers/browse/samples/spa-react-minimal
  2.  In Magnolia author check if the site does correctly the call to retrieve the template annotations and add components to areas
  3. Remove secondary area from light module https://git.magnolia-cms.com/projects/MODULES/repos/frontend-helpers/browse/samples/spa-react-minimal/light-modules/sample-light-module/templates/pages/standard.yaml#25
  4. In Magnolia author no longer we can edit anything

Expected results

Users can still modify all remaining areas

Actual results

Template annotations endpoint returns error:
code: "unknown"
message: "Area secondary is not defined in template definition of node /spa-home"
Preventing Magnolia from rendering green bars.

Workaround

Development notes


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