Harmonize SiteAwareTemplateAvailability (MGNLSITE-34)

[MGNLSITE-33] SiteAwareTemplateAvailability only works with renderType=site and thus prohibits usage of other renderers in a site definition Created: 21/Aug/15  Updated: 23/Feb/16  Resolved: 19/Feb/16

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

Type: Sub-task Priority: Major
Reporter: Philip Mundt Assignee: Ngoc Nguyenthanh
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 4.5h
Time Spent: 3d 6.5h
Original Estimate: 5d

Issue Links:
Relates
relates to MGNLSITE-43 Site aware renderer for any renderer Closed
causality
dependency
is depended upon by BLOSSOM-222 Integration with site module Closed
duplicate
is duplicated by MGNLSITE-42 Allow site definition template availa... Closed
Template:
Date of First Response:
Sprint: Saigon 32

 Description   

Current SiteAwareTemplateAvailability proves to be too restrictive when working with e.g. jsp (sub-) templates. It used to be possible to combine various templates / renderTypes in one site definition.

Additional details from Tobias:
Allow site definition template availability on templates not using the site renderer.
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 ]

Merged in description from https://jira.magnolia-cms.com/browse/MGNLSITE-42 which I closed as duplicate.

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