Bug #21832
closed
All top-level pages in site menu by default
Added by Colin McDonald 3 months ago.
Updated 2 months ago.
Description
The https://pcp.gc.cuny.edu/ team let me know that their menu is showing all of their published top-level pages in the top nav. No resaving the menu, changing the menu structure, etc. seems to change it.
I already made sure that the "Automatically add new top-level pages to this menu" setting in Appearance > Menus is not checked. Maybe it's also worth noting that the site still uses Twenty Eleven as its theme.
For some reason, while logged out or logged in in a normal Chrome window I see the correct short menu of the site (see attached), but while logged out or logged in in a private window I see the long incorrect menu (also attached).
Files
- Status changed from New to Testing Required
- Target version set to Not tracked
The static page cache was not purging. I guess this means that the litespeed-cache plugin doesn't invalidate on menu-related items. I'm adding this to my list (which I was literally working on as this email came in).
See #21826
Ok, thanks. Glad to get this on the list before it went out. Looks fine to me now in a private window.
- Status changed from Testing Required to Resolved
Follow up that this user reports additional changes they've made to the https://pcp.gc.cuny.edu/ menu are not appearing. I've confirmed that these changes exist in Appearance > Menus but aren't showing on the homepage in a private window:
- "Fellowships and Eligibility" label appearing instead of just "Fellowships"
- "Resources" item appearing when it's been removed
The user has future menu changes in progress, too. Is this one we'll get to a point where it "just works" as far as purging and displaying the latest version? Is there anything else the user should do to force the changes?
I've purged the cache manually again.
I don't know whether the blog admin has access to https://pcp.gc.cuny.edu/wp-admin/admin.php?page=litespeed-toolbox, but if so, they can use the Purge All button when this occurs. Otherwise they'll have to pass requests along to us for the time being.
This problem will go away with the custom tools described in #21833, but we are likely weeks away from those tools being ready to roll out.
- Related to Feature #21833: Custom page purging and other customizations for Litespeed Cache plugin added
Thanks, Boone. I am also an admin of this site, and I can access that link, so the user should be able to as well. I'll let them know about the Purge All interim solution.
Also available in: Atom
PDF
