[PAGES-1221] Template annotation endpoint should return all defined areas Created: 08/Jun/23  Updated: 12/Jun/23  Resolved: 12/Jun/23

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

Type: Bug Priority: Neutral
Reporter: Robert Šiška Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-1222 Implementation Sub-task To Do  
PAGES-1223 Review Sub-task To Do  
PAGES-1224 Pre-Integration QA Sub-task To Do  
PAGES-1225 QA Sub-task To Do  
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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce:

 * Create an new SPA page.
 * Add new area to the page definition and render it in your SPA.

Expected results: Area should be "provisioned" based on the annotations endpoint, even when it doesn't exist in the content (see MGNLFE-117)

Actual results: Missing area content cannot be provisioned and the area content is undefined in SPA.

Notes: The annotation endpoint should return all areas defined in the page template, not just those already existing in the content.

Norsu only. JCR behaves as expected.



 Comments   
Comment by Jaroslav Simak [ 12/Jun/23 ]

Duplicate of SAAS-61.

Comment by Matt Rajkovic [ 12/Jun/23 ]

Closed as duplicate of: https://magnolia-cms.atlassian.net/browse/SAAS-61

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