-
Bug
-
Resolution: Fixed
-
Critical
-
4.5.2
-
None
-
None
In older versions we supported so called sub templates (selected based on file name extension). In 4.5 we have introduced the more powerful template variations but our default implementation does only consider the channel.
But it should use the following lookup for template variation names
- channel-extension
- extension
- channel
Then instead of the two subclasses we should ship one which combines them: RenderableVariationResolver.
Acceptance criteria
- is causing
-
DOCU-304 Documentation for subtemplates being treated same as variations since 4.5
- Closed
- is related to
-
MGNLSTK-1210 default site variation resolvers should consider the extension
- Closed