Quote from: landonpoburan at Feb 16, 2011, 08:30 PM
Quote from: goonz at Feb 16, 2011, 08:26 PM
What about trying to use &parentRowTpl to see if that fixes the glitch? Then you could change your Tpl (for parentRow) to read as such:
**removed code
This may help in pinpointing if there is some setting wrong in the site, or if it is a glitch in WF.
Would I use this instead of &rowTpl or use both together?
Both together. Wayfinder would use rowTpl for Resources that are not containers, and parentRowTpl would be used for resources that are containers and have children.
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein
Quote from: ottogal at Feb 16, 2011, 08:27 PM
@samba:
I’ve never used "class=" before wf.classnames, Wayfinder should fill that in for you.
That’s wrong. This is the case for wf.classes (see sottwell’s reply).
<li[[+wf.id]] [[+wf.classnames]] n[[+wf.docid]]">
cannot be correct syntax. You see it already from the fact that you have a single " in it.
You’re right about the paren... I forgot he’s piling up multiple classes in there. But you can indeed avoid using "class=" on a typical Wayfinder call if you want to.
http://muddydogpaws.com/development/wayfinder/parameters.html
Quote from: goonz at Feb 16, 2011, 08:37 PM
Quote from: landonpoburan at Feb 16, 2011, 08:30 PM
Quote from: goonz at Feb 16, 2011, 08:26 PM
What about trying to use &parentRowTpl to see if that fixes the glitch? Then you could change your Tpl (for parentRow) to read as such:
**removed code
This may help in pinpointing if there is some setting wrong in the site, or if it is a glitch in WF.
Would I use this instead of &rowTpl or use both together?
Both together. Wayfinder would use rowTpl for Resources that are not containers, and parentRowTpl would be used for resources that are containers and have children.
Thank you very much. I added in the &parentRowTpl and removed &parentClass=`parent` and it eliminated the arrow beside the 1 that had no children. But still had the issue of no arrow beside the one that had children. So I checked and it didn’t have "Container" check off. So I checked it off and now it works. So not sure why that page wasn’t a container when it had children but its all good now.
