WayFinder Weirdness? UltimateParent problems? Published pages not visible?

I've got a very complex MODx site that's hit several snags -- and I'm seeing some weird behavior. Hopefully they eyes of the forum folks will help spot what it is... here goes...

When one user logs in, they should see a full list of all the pages they have access to. Instead they see MOST of the pages they should have access to. WayFinder is generating a menu, but it's missing a few pages.

Here's what the WayFinder call looks like:



That's a hot mess, but 2 important things to note:
1. The UltimateParent call in the HTML comment DOES output the correct page id, e.g. 123.
2. When the WayFinder call uses the page id EXPLICITY in the startId parameter, it DOES return all pages, including the ones that went AWOL with the above call.

In other words, specifying the startId as an integer works, like this:



So UltimateParent is printing the correct ID, WayFinder is printing the correct menu with all pages when you pass it an integer page ID, but when you use UltimateParent to pass the startId, it misses some pages. WTF?

This makes no sense to me... even if the cache were not being cleared correctly, why would SOME pages be shown when others would not? I'm not even sure what to try here.

And the final bit of weirdness... the missing pages are published and they belong to the correct resource groups, but if you try to view one of them as a logged in user (who has access to the other pages in the same resource groups), the request 404s. If this were only a WayFinder or caching issue, then you should be able to navigate to the page directly. So it's like MODx thinks the page isn't published when it is.


Anyone have any ideas? Thanks. [ed. note: Everettg_99 last edited this post 15 years ago.]

AHA. Stupid mistake (like always). I was seeing "inconsistent" behavior because I was checking the WayFinder call while logged into the manager. So this turned out to be a simple permissions error: I had linked up the wrong ResourceGroup to the UserGroup. Whoops. Once I fixed that, it all seemed to work.