Posted: May 28, 2018 at 9:37 pm
wp-debug gives this error:
Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘The namespace for this manifest file has already been registered, choose a namespace other than event-espresso-core-regespressophp’ in /home/myrbsch1/public_html/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php:463
all I get on nav-menu.php is a blank page. help please!
That’s strange and looks like a theme or plugin conflict.
If you install the Health Check plugin on the site.
Go to Dashboard -> Health check
Then Troubleshooting -> Enable Troubleshooting mode – http://take.ms/CcaZL
That will disable all other plugins and switch you to a default theme but only for you and not your sites visitors.
Now your in troubleshooting mode in the admin bar go to Troubleshooting mode -> Plugins -> enable event-espreso-core-reg – http://take.ms/q91hA
Test setting the nav menu now, does it work?
If so, in the Troubleshooting bar again, select, ‘Use current theme’
Again, retest, does it show an error now?
Well, before you sent this I needed to update a menu so I disabled Event Espresso and the nav-menu.php came back up with no errors. I haven’t updated the theme in well over a month and this is a brand new error.
I will try the steps you requested when I get to my office this afternoon.
It will as the error is coming from Event Espresso, however, it’s not happening on any of my test sites so it’s not a conflict with just EE and WP, but a plugin or the theme.
It could be something we have changed that now conflicts with the theme (or a plugin) on your site. But we’ll need to know where the conflict is to be able to fix it.
OK. I loaded Health Check. I went into Troubleshooting mode and nav-menu.php works with and without event-espresso-core enabled on both the default theme and my current theme. When exiting, I still get this from wp-debug:
Fatal error: Uncaught InvalidArgumentException: The namespace for this manifest file has already been registered, choose a namespace other than event-espresso-core-regespressophp in /home/myrbsch1/public_html/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php:463 Stack trace:
#0 /home/myrbsch1/public_html/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php(444): EventEspresso\core\services\assets\Registry->registerManifestFile(‘event-espresso-…’, ‘http://www.rbsc…’, ‘/home/myrbsch1/…’)
#1 /home/myrbsch1/public_html/wp-includes/class-wp-hook.php(286): EventEspresso\core\services\assets\Registry->registerManifestFiles(‘widgets.php’)
#2 /home/myrbsch1/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#3 /home/myrbsch1/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#4 /home/myrbsch1/public_html/wp-content/plugins/wp-megamenu/classes/class.wp-megamenu-base.php(59): do_action(‘admin_enqueue_s…’, ‘widgets.php’)
#5 /ho in /home/myrbsch1/public_html/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php on line 463
I am going to go back into troubleshooting mode and try enabling addons one at a time to see if I can find the conflict.
I did some digging and it’s the WP Mega menu plugin that’s causing the problem, its firing hooks for the sidebar menu on the nav-menus.php hook and I can’t see any way to prevent that from happening in their code without basically disabling WP Mega Menu at the same time.
I’m not sure if we can prevent the above error in EE but have requested some feedback from our developers to confirm.
Just to note we added a fix for this in the latest version of EE (4.9.63 at the time of this reply).
Please update the version of EE you are using on the site and it should prevent the above.
The support post ‘Nav-Menu.php won't load’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.