[MGNLSITE-42] Allow site definition template availability on templates not using the site renderer Created: 25/Sep/15  Updated: 19/Nov/15  Resolved: 19/Nov/15

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

Type: New Feature Priority: Major
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-34 Harmonize SiteAwareTemplateAvailability Closed
relates to MGNLSITE-43 Site aware renderer for any renderer Closed
duplicate
duplicates MGNLSITE-33 SiteAwareTemplateAvailability only wo... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

This is kind of a big change but it would make sense to use the template availability configuration on the site definition also for templates not using the site renderer.

For instance plain text templates or jsp templates.

And for Blossom templates which is a special case in that those templates use the blossom renderer to call into Spring and then render their views using the site renderer. In this scenario SiteAwareTemplateAvailability checks the render type and sees blossom and therefor fallback to the default template availability strategy.



 Comments   
Comment by Christopher Zimmermann [ 19/Nov/15 ]

Closed as duplicate (https://jira.magnolia-cms.com/browse/MGNLSITE-33) because it's confusing to have many overlapping tickets.

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