What am I missing here?
The first menu lists the site’s main home page and the contact page - works fine.
The second should list the parent of the current page and all the siblings of that page.
It lists the siblings, but not the parent. I tried hard-coding the parent ID (11) and calling them both un-cached but the second Wayfinder call always fails to show a link to the parent. :’(
[[Wayfinder? &startId=`0` &level=`1` &includeDocs=`1,6`]]
[[Wayfinder? &startId=`[*parent*]` &level=`2`]]
Bob
-
☆ A M B ☆
- 24,524 Posts
That’s because by default Wayfinder does not make an entry for the parent document (the one whose ID you give it). There is a parameter to do that, &displayStart. Assign a template for it with &startItemTpl.
I strongly recommend browsing through the documentation for Wayfinder to see all of the options it has.
BobRay: the calls work fine on my test server. Just copied them into the content and there I had the two menus as specified. Are you sure that you are in a page that has a parent and is published?
Quote from: dev_cw at Jan 26, 2008, 06:12 AM
BobRay: the calls work fine on my test server. Just copied them into the content and there I had the two menus as specified. Are you sure that you are in a page that has a parent and is published?
http://bobsguides.com/modx-links.html
The main MODx page is definitely its parent and it’s published but.
Bob
Quote from: sottwell at Jan 26, 2008, 03:03 AM
That’s because by default Wayfinder does not make an entry for the parent document (the one whose ID you give it). There is a parameter to do that, &displayStart. Assign a template for it with &startItemTpl.
I strongly recommend browsing through the documentation for Wayfinder to see all of the options it has.
Thanks Susan. Using &displayStart does put the parent up but it’s styled as H2 and it’s not a link.
I guess I’ll have to dig a little deeper into tpl land (one of my major MODx weak spots).
Bob
