Wayfinder only works with actual children of parent

Quote from: sottwell at Jan 02, 2013, 01:55 PM

Well, as far as permissions go, I have no clue. That is still black voodoo to me.

I agree. Thanks for weighing in. If I get this sorted, I'll post the solution.

If permissions are black voodoo for you (like for me, too), then it's rather improbable you used them, and so I presume other reasons for the issue.

The pages About Linfield and Department Directory, are they really using the same template? Did you double-check that the spelling of &startId is correct?

How is your complete Wayfinder call?
What are the template chunks used for the properties?

By the way, you should also have an eye on validation:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.linfield.edu%2Fdepartment-directory.html

Quote from: ottogal at Jan 02, 2013, 11:11 PM

If permissions are black voodoo for you (like for me, too), then it's rather improbable you used them, and so I presume other reasons for the issue.

The pages About Linfield and Department Directory, are they really using the same template? Did you double-check that the spelling of &startId is correct?

How is your complete Wayfinder call?
What are the template chunks used for the properties?

By the way, you should also have an eye on validation:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.linfield.edu%2Fdepartment-directory.html

The department directory is using a duplicate of the "about" page template so I can mess with it. The full wayfinder call is this: [[!Wayfinder?startId=`945`&hideSubMenus=`true` &level=`2`]]

Yeah, validation. All the errors are in the breadcrumb chunk. Changing the doctype will probably clear that up. We're moving to html5 even as we speak. Even on a good day, pages fail all the time. It's like herding cats here!

SOLVED!
I wish I could say it was some software bug but as HAL would say "It's always the result of human error." Looking at the wayfinder call I pasted above, I was missing the "&" in front of the startId. That actually wasn't killing it. The &hideSubMenus=`true` should have had a value of `0` or `1`. That broke it. Hiding in plain sight.

Thank you all for the help. If forced me to keep looking at it and trying tests that included pasting code from working installations which exposed the errors. I hope I can return the favor one day.

Glad you found the solution.

By the way:
If the &startId property is missing, say like in this call:then WF chooses the ID of the actual page as &startId, resulting in the same output asThat equally happens if the property name is misspelled.

I checked again your Department Directory page and found a new issue with text overlay in the breadcrumb line - see this image.

Quote from: ottogal at Jan 03, 2013, 09:36 PM

Glad you found the solution.

By the way:
If the &startId property is missing, say like in this call:

[[Wayfinder? &level=`2`]]

then WF chooses the ID of the actual page as &startId, resulting in the same output as

[[Wayfinder? &startId=`[[*id]]` &level=`2`]]

That equally happens if the property name is misspelled.

Thanks for the clarification. BTW, the breadcrumbs display issue is resolved. It was still in the test template and I've been fixing the <ul> - <span> validation issue with that package. This has turned out to be a productive week!