Hello all,
I’d like to use the IncludeDocs parameter with Wayfinder to build out the primary navigation for a site, but it seems Wayfinder is set up to automatically exclude any submenus of the included documents.
Is this the case?
I figure that these are the main criteria for this primary navigation:
1. All changes to navigation are implemented by changing document properties. (changing link text by changing menutitles) This way no one has to mess with code.
2. When new child docs of items in the navigation are created, they should automatically be in the navigation.
3. But newly created documents that aren’t child docs of documents currently in the primary nav shouldn’t automatically be inserted into the primary nav.
So considering these criteria, I came to the solution that using includeDocs would work. No other newly created documents would be inserted into the navigation this way, unless they were child docs of documents already in the nav. I thought about just using excludeDocs to exclude stuff i don’t want in the nav, but then when new docs are created they have to be added to the wayfinder call. So I don’t want to do that.
So it seems that if includeDocs would just build out submenus as well, that would be the best solution all around.
Here’s the Wayfinder call I’m using:
[!Wayfinder? &startId=`0` &level=`0` &outerTpl=`outerTpl` &innerTpl=`innerTpl` &rowTpl=`rowTpl`
&innerRowTpl=`innerRowTpl` &firstClass=`first` &lastClass=`last` &includeDocs=`7,6,16,17,19,20`!]
Has anyone come across this problem and found a good solution?
MODX Staff
