Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
None
Description
When on a concrete template (like stkArticle) you add a variation (like smartphone) and you want to disable the navigation it does not work.
But if you disabled the navigation from the site definition variation, then it works... so it really seems that the variations merge does not work properly with a concrete template. The site definition variation wins against the template variation.
How to reproduce:
- setup an environment with Mgnl 4.5.3 and the corresponding version of the demo-project.
- replace stkArticle with the attached config.
- render this page http://localhost:8080/magnolia-enterprise-webapp/demo-project/about/history.html?mgnlIntercept=PREVIEW&mgnlPreview=true&mgnlChannel=smartphone
- check at the bottom, you must see the navigation
Now you can try to disable the horizontal and vertical navigation from the variation smartphone defined on the site defintion level. Then it will work, no more navigation !!
So for me it's a bug because at the end the configuration defined on a concrete template must win against the others.
//jsimak
Moved to documentation. It is not a bug - see attached screenshot how to configure variation.
It is not working if we don't specify class and set it to STKPage. If we do not specify it then ConfiguredTemplateDefiniton is used to store variation node but it doesn't have navigation variable so content2bean can't set it. Reason why it works with STKPage is that this class has navigation variable defined.