-
- 74 Posts
Tried it, didn't work. The page itself is not cached, I've always thought you're supposed to call Snippets with the inverse of their document's cache setting. I'm currently mucking about with Wayfinder Property sets - maybe the default set is the problem?
Edit: I've never had a problem like this before on Evo, so I'm really stumped.
-
- 793 Posts
It's difficult to help without knowing the resource tree. Are all the 8 documents children of resource 0? Are the missing documents the ones you added latest?
-
- 128 Posts
Look at the code... are they just not showing or are they not rendering?
I LOVE MODX! | greyskymedia.com
-
- 74 Posts
Yeah, there are 8 available pages, all direct children of the Web context.
I can hide one of the 4 pages that is currently showing, save, and the menu updates to hide that document, so I don't think it's a caching issue. There's something deeper preventing new and old pages from being shown.
Edit: I've looked at the raw HTML, there are only the same 4 documents in the UL list. There's nothing being hidden by CSS. However, I know that there is a JS menu involved, maybe I'll look into that (JS could be modifying the DOM?)
-
- 74 Posts
Some screenshots so that you all don't think I'm making this up.
doc-tree
This is the document tree, you can see that all pages are marked Show In Menu.
wayfinder
This is the actual output WF menu. The Home Page is correctly hidden, but you can see that Sign In, Facebook, Twitter and Tags is incorrectly hidden.
I can correctly toggle Show In Menu on/off for all documents you see appearing in the WF menu.
UPDATE
If I explicitly set &includeDocs to the IDs of the 4 missing documents, nothing is output to the WF menu. With &debug=`1`, no documents are shown at the bottom of the debug output.
First, try getting a plain HTML nested list, without any Javascript involved. Although if your View Source isn't showing them, the Javascript shouldn't be the problem.
Are the menutitles the same as the pagetitles? Are you doing anything with users/groups?
As far as snippets being called cached/uncached, any snippet that will return dynamic content, such as a snippet that depends on the current date, or user validation, or form input, needs to be uncached. Anything else, especially listing snippets like Wayfinder or getResources, should be cached. The only reason I can think of that Wayfinder should be called uncached is if you're dealing with user logins, and the menu needs to be different for logged-in users and anonymous users.
-
- 74 Posts
I meant to post this but forgot. I disabled the JS menu and the problem didn't go away, this was confirmed by the WF Debug Output, which did not show the missing documents. This means they are being blocked at the WF end (or before?)
The snippet is called cached on an uncached page.
No document/user groups are in effect.