flipty

BTW this effectively solves the issue for me so I am marking it solved.

UPDATE: I noticed that a few of the sites I have worked on seemed to be able (in WP 6.0.2) to work as normal after the 6.0 update. What I was doing was forcing navigation to function as it used to by adding the register_nav_menus() function to my functions.php:

register_nav_menus(array(
  'menu-1' => esc_html__('Primary', 'text-domain')
));

I am having this same problem, and I am assuming that the WordPress core team have abandoned the “classic” way of creating and editing menus.

For the time being, on themes that I created, I am making a custom ACF menu function that replicates the Classic Menu. I can’t wait around in hopes that the WP Core will change and finally allow my customers to edit their menus.

I had to move several of my high-uptime-requirement WP sites off of DreamHost and onto WPEngine because of this issue more than a year ago.

What was happening then (and probably still is) per the DreamHost support techs is that there is a temporary directory on the shared hosting environment(s) that is being filled up and is not automatically emptied, causing the sites to be completely unresponsive. I was calling DH every few days during prime restaurant hours (several of my clients are restaurants with online ordering) and begging them to clear the temp directory without having to wait for them to suggest 5 other things that were NOT the problem. It’s not that they weren’t being helpful, it’s that every time I called the tech on duty would have to re-troubleshoot it because I was just some guy telling them what to do…

I am pretty sure that DreamHost DOES have dedicated WordPress hosting, which is more solid than just throwing WP installs onto their standard non-specialized plan (aka, the one I pay $10 monthly for and host like 30 sites on…) — so you definitely get what you pay for.

Move critical sites over to a WP-specific plan, or pay the big bucks, go with WPEngine and never have to think about it again.

This is extremely frustrating, as I have dozens of custom themed sites I developed and support, and now all of the sudden I am trapped at WP 5.9.3 in order to edit the navigation. Not a big deal for some sites, but crucial for others.

For me, wp_nav_menu() *does* work, but I have no way to actually edit the menu, so it is frozen in whatever state it was in when WP 6.0 was installed.

A ridiculous design decision. Following this thread in case there is more information.

I am seeing the same issue on all sites running WP6.0, locally I am running MAMP with PHP 7.3.29 and on WPEngine I’m running into the same issue with PHP 7.4 or PHP 8.

I should add, if I try to directly go to the nav editing URL I get the error message “Your theme does not support navigation menus or widgets.”

Sorry about the delayed response, the notification got caught in my spam folder.

• This reply was modified 2 years, 4 months ago by flipty.

Thank you Ian, excellent advice!

Thank you, I appreciate it!

Hello Angelo, I think I am starting to see where the issue is.

The podcast is initially uploaded to Podbean and hosted there. Then I use PowerPress to import the episode(s) to my custom WP site. Within Podbean’s site, there is an episode number for each episode, but it is looking like it does not get brought over in the import process, meaning that the PowerPress’ episode numbering is blank on the WP side.

I’m sure if I edit the Episode # within PowerPress, it will show up. Ideally I am hoping to skip that step and have the Episode # from PodBean be populated into the PowerPress episode_no field.

Thank you for the information, you have a great plugin!

Hello Angelo, I do not see episode_no in a var dump of the powerpress_get_enclosure_data()

I checked, each episode has a number set within Podbean, but the episode number doesn’t seem to get sent along with the other metadata.

Thank you for the quick response, I look forward to (hopefully) a solution. You’d hate to see the extra work I’m doing to “number” the episodes via a set of relatively complicated queries.

That worked AMAZINGLY. Thank you!!

Wow, even if this *does not* work I commend you on your excellent support! I will try it out and report back.

I already have ??

I think let’s close it. Thank you for your fantastic support, Thomas!