Think about it in terms of walking the tree. The '..' parent operator
takes you up to the parent of both index and page1, then down to index
and to logo.
Without that, index/logo is most likely assumed to be at /page1/index/logo.
I'm sure there's an operator for the sibling axis in the spec that would
probably work as well.
--David
Amir Mistric wrote:
Hello Magnolia experts
I am trying to figure out use of relative urls in includeTemplate tag.
I have 2 pages
/index
/page1
/index page has a contentNode logo (/index/logo) created by paragraph which I
want to include on page1 so on page1 I have:
<cms:includeTemplate contentNodeName="index/logo" />
This however, does not work until I put in a relative?? path of <cms:includeTemplate
contentNodeName="../index/logo" />
I am ok with relative path part but why does relative path have to start with
../ if the pages are on the same level?
Does anyone know?
Thanks
Amir
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
