- This topic has 11 replies, 2 voices, and was last updated 3 years, 2 months ago by Tom.
February 22, 2018 at 7:30 am #502924drew
I’ve noticed an unusual issue where nav menu titles are being replaced by the nav menu id# and display “no title”
- When viewing the menu items from any URL that does not contain the subdirectory, the title displays fine: https://www.screencast.com/t/W79z9NTO4e
- When viewing the same submenu from a URL that contains the subdirectory, the nav menu label gets replaced with the ID# and (no title): https://www.screencast.com/t/IlbH9q32Dq
Here are some test pages to reproduce:
Everything is fine: https://apollosfire.org/
Issue appears: https://apollosfire.org/event/50-ways-to-leave-your-lover/
DrewGeneratePress 2.0.2GP Premium 1.5.6February 22, 2018 at 11:44 am #503107TomLead DeveloperLead Developer
This is likely an issue with Ubermenu, as it looks like you’re using them to build the menu.
Might be worth checking with their support 🙂February 22, 2018 at 2:07 pm #503217drew
Gotcha although how did you troubleshoot that? I’m curious to know more about how best to determine which direction to look first.February 22, 2018 at 8:20 pm #503367TomLead DeveloperLead Developer
I right clicked the element and clicked “Inspect”, which shows the HTML. It has tons of ubermenu classes, which means they’re taking over the output of the menu.February 23, 2018 at 8:29 am #503835drew
Hey Tom, I completely deactivated ubermenu but am still having this issue, any thoughts?February 23, 2018 at 10:03 am #503917TomLead DeveloperLead DeveloperFebruary 23, 2018 at 10:19 am #503932drew
NP, I pushed everything over to a staging install and the only plguing left activated are GP Premium and the event manager (otehrwise those sub menu items don’t appear and we therefore can’t test): https://www.screencast.com/t/8GH2l5FQ
The issue still persists (which you can check directly at) – http://apollosfire.staging.wpengine.com/event/50-ways-to-leave-your-lover/
As for the event manager, that’s my plugin and we’ve been checking it on all of the installs (more than 70 which run nearly identical configs to this install) and the issue doesn’t exist on any of those.
Have you ever experienced a menu item issue like this via custom post types?February 23, 2018 at 9:21 pm #504260TomLead DeveloperLead Developer
Super strange. Might be worth scrapping that menu and re-building it from scratch.
WordPress is 100% responsible for the menu, the theme just calls it with a built in function.
You may just be able to remove those affected menu items and add those specific pages back in.February 24, 2018 at 10:33 am #504670drew
Super stange indeed. I implemented a few different variables to see about pegging down the issue and everything actually turned up more questions than not:
- Create a custom link version of the menu item. This produced the correct results across each test. But having to use a custom link option isn’t exactly best practice.
- Creating new versions of the menu item using it’s custom post type. This produced inconsistent results. Sometimes it worked as expected but other times it produce the bug.
I also tested using custom post types other than the “events” CPT. They had similar degrees of hit and miss consistency.
Lastly, as an added measure I tested on Twenty-Seventeen and the issue persists there as well (I left that theme up on the staging site for you to see if needed: http://apollosfire.staging.wpengine.com/event/christmas-on-sugarloaf-mountain/)
So yes, super strange and above my current skills pay grade. 🙂
Suggestions?February 24, 2018 at 8:29 pm #504898TomLead DeveloperLead Developer
Perhaps there’s something wrong with those actual pages? Try re-saving them and confirming they each have a post title.
If that doesn’t work, maybe re-create them and delete the old ones.February 25, 2018 at 9:51 am #505275drew
Thanks, we’ll keep digging into it. I’ve been searching the wordpress trac for similar items but haven’t turned up anything exactly along these lines, have you?February 25, 2018 at 10:52 pm #505638TomLead DeveloperLead Developer
I’ve never seen it. From a code stand point, it’s like the menu is calling to the wrong ID in the database.
That’s why I think deleting them and starting fresh with those pages might fix it.
- You must be logged in to reply to this topic.