[MAGNOLIA-5915] Custom Home page template is not available when creating new home page Created: 10/Sep/14  Updated: 02/Jul/18  Resolved: 02/Jul/18

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

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:

 Description   

You can use only "Home" or "Redirect" templates when creating new home page since those are defined in "Default" site. Only after creation of the home page and when name of the page is matching site configuration providing extra home page template one can assign correct template to it. This is very cumbersome and dangerous since opening such page with incorrect template might result in auto creation of components that can't be deleted without accessing JCR Browser and might render such homepage unusable once it has correct template assigned.



 Comments   
Comment by Jan Haderka [ 11/Sep/14 ]

This is not a WCSI bug, but Magnolia bug.

Comment by Magnolia International [ 11/Sep/14 ]

So that means you have to create the home page before the site configuration is taken into account. At the same time, I don't know how else it'd work, except with a "meta" app to create sites (which would create the site def AND its home page, for instance)

Comment by Jan Haderka [ 11/Sep/14 ]

yeah, that would be perhaps ultimate solution ... or we scan and allow all home pages at the root level regardless them matching the name defined in mapping of the site.

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