Hi Adam
In this case def is a reference to the page definition, whereas when you try
this in the footer, you are already inside an area and hence accessing the def
of the area. That's why it is not working just like that. However, you can make
use of the contextAttributes to pass on properties from the main.ftl to the
footer area. E.g.:
[code][@cms.area name="footer"
contextAttributes={"navigationScript":def.navigation.horizontal.template}/][/code]
and inside the footer area script you can include the navigation script like
this:
[code][#include ctx.navigationScript ][/code]
But you will still have an issue with the horizontalNavigation script itself.
If used on the page, it works, but if you use it inside the footer it will tell
you that model.navigation is undefined. Same issue as before: scope - in the
footer model references the footer model and not the page model anymore. So
what you can do is test first if model.navigation has content or exists, if
not, replace all occurrences of [b]model.navigation[/b] with
[b]model.root.navigation[/b].
HTH
Natascha
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=081adbc4-9944-4953-8f95-7327d4c0d568
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
