[MGNLSITE-13] If the site template availability is not configured - then all page templates are available Created: 17/Mar/15  Updated: 20/Mar/15  Resolved: 18/Mar/15

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

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6132 Rename ConfiguredTemplateAvailability... 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)
Release notes required:
Yes
Date of First Response:

 Description   

Currently if you use the site module - then you must configure each of your page templates at /modules/site/config/site/templates/availability/templates in order for them to be available in the page editor. As we want to make using and especially getting started with Magnolia as easy as possible - we will remove the necessity to configure the page templates at this node.
-
If the /modules/site/config/site/templates/availability node does not exist, all pages will be available.

As soon as the node is present - than only the pages configured here will be available - the familiar behaviour adopted from STK site availabillity.


Generated at Mon Feb 12 07:11:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.