Wayfinder only works with actual children of parent

I have three Modx Revo 2.2.6 installations. Wayfinder works just fine in two of them. In the third, largest installation, Wayfinder will only work with a parent resource's actual child resources. So if a document has a resource ID of 53, Wayfinder will only display a menu if the parent ID is 53. If you use a different parent ID from another resource/children group, the menu does not display. This doesn't happen in my other installations.
The problem appeared after a very complex migration from Evolution and has persisted through several upgrades and a reinstallation of Wayfinder. Any ideas as to what is going on here would be very welcome. I'm out of ideas.

Thanks so much.

The children of the &startId resource must be published, must show in the menu, and a user must have web-context permissions to view it. It's most likely a permissions issue; Revo permissions aren't the easiest to deal with.

Quote from: sottwell at Dec 21, 2012, 10:01 PM

The children of the &startId resource must be published, must show in the menu, and a user must have web-context permissions to view it. It's most likely a permissions issue; Revo permissions aren't the easiest to deal with.

Sorry to be slow responding. That Holiday thing, you know. Hope yours was grand.
All the resources are published and are web visible. That's the odd thing. If I have two resources, say with ID's of 53 and 75 and they both have children. They will show all of their children just fine in the wayfinder menu provided I've assigned resource 53's &startID as 53 and resource 75 &startID as 75. If I try to assign resource 53's &startID as 75, I get nothing. The problem occurs with all resources in this site, which is someplace north of 8000.
This is an issue mainly with general resources like 404 pages, "about us" pages and site map pages where we would have a common set of resources we would send them to. The workaround has been to build weblinks as children of those resources but it's a pain to maintain over the whole site.

So if you have a completely unrelated page, and use startId=`57` or startId=`53` you get nothing?

Anywhere you put startId=`xx` you should get a list of all the children of resource xx.

Quote from: sottwell at Jan 02, 2013, 12:34 PM

So if you have a completely unrelated page, and use startId=`57` or startId=`53` you get nothing?

Anywhere you put startId=`xx` you should get a list of all the children of resource xx.

That's correct. For a live example, if you look at: http://www.linfield.edu/department-directory.html
That's using the &startID for this resource: http://www.linfield.edu/about.html
The second resource's menu works and is using it's own id as the &startID. BTW, I'm setting the &startID's as a template variable. I'm going to try some experiments using hard coded id's and see what that does.

Have you tested your TV to make sure it's returning the value you expect?

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

Have you tested your TV to make sure it's returning the value you expect?

I've removed the TV and replaced it with a hard coded &startID and I get the same result. I'm using the addresses above as test beds.

Well, I can't see any reason why it's not working as expected. I presume the &startID is a typo in your post; in the snippet it's supposed to be &startId

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

Well, I can't see any reason why it's not working as expected. I presume the &startID is a typo in your post; in the snippet it's supposed to be &startId

One should never presume anything with my typing skills, but in this case, it was a typo in my post. The template is correct.
I also created a child for the test page, changed the resource &startId to test page's ID in the hard-coded test template and the child appeared in the menu.
Going back to your suggestion that it's a permission issue, is it possible in either system settings or access controls to limit visibility only to a resources actual children? I'm comparing settings now between this site and the ones where this isn't an issue but so far I haven't seen any differences.

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