[MGNLDEMO-351] SPA renderer pages are not available by default on demo bundles Created: 04/Nov/20  Updated: 08/Jan/21  Resolved: 15/Dec/20

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 1.5.2
Fix Version/s: 1.5.2

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: Not Specified

Attachments: PNG File site-spa.png    
Issue Links:
relation
is related to MGNLDEMO-356 SPA renderer pages are not available ... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: SPA Editor
Sprint: HL & LD 17, HL & LD 18, HL & LD 19
Story Points: 2

 Description   

On a demo bundle, (ce or dxcore),  page templates with "renderType: spa" are not available to be selected when one creates a new page in the pages app. This is an obstacle for developers trying out the SPA feature.

Be default, on the demo bundles, provisioned templates with "renderType: spa" should be available.

To reproduce:

  • Install CE demo bundle
  • Create a page template (or use an existing page template) and set the renderType:spa and 
    class: info.magnolia.rendering.spa.renderer.SpaRenderableDefinition
  • Open pages app
  • Add page
  • Note that your page template is not available.

On 6.2.0 this problem was not present, one was able to add SPA pages by default. 

This seems to be due to the site configuration.

On the ce demo bundle, the enableAllWithRenderType node only has freemarker and jsp values.

 


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