-
Improvement
-
Resolution: Fixed
-
Neutral
-
1.0.2
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Kromeriz 30
-
2
It is currently only possible to use the template prototype configured on a site when using Freemarker templates. This is because the site module only has one renderer that is based on FreemarkerRenderer.
To support JSPs we need a SiteAwareJspRenderer. It would need to have a specific renderType, for instance site-jsp.
Info
The main functionality that the SiteAwareFreemarkerRenderer adds is the capability to merge page's template definition with a prototype template definition from the site and/or a fallback template definiton when specified.
Possible solutions
Duplicating functionality from SiteAwareFreemarkerRenderer- Create a new wrapped renderer that will delegate to another renderer, here the freemarker or jsp renderer
- is causing
-
MGNLCAT-164 No need to install ctx attributes on site renderer since MGNLSITE-43
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
MAGNOLIA-6530 Freemarker and Site renderer and not consistent regarding node wrapping
-
- Closed
-
-
MGNLSITE-42 Allow site definition template availability on templates not using the site renderer
-
- Closed
-
-
MGNLSITE-33 SiteAwareTemplateAvailability only works with renderType=site and thus prohibits usage of other renderers in a site definition
-
- Closed
-
