|
Austin Ginder
|
June 4, 2018 at 2:34 pm
When I attempt to go to the WordPress menu page I receive a white screen. Below is the copied error from the error log. Looks like Event Espresso v4.9.62.p is in conflict with Max Mega Menu v2.4.2. Any recommendations?
Fatal error: Uncaught InvalidArgumentException: The namespace for this manifest file has already been registered, choose a namespace other than event-espresso-core-regespressophp in /nas/content/staging/perfectimage/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php:463 Stack trace: #0 /nas/content/staging/perfectimage/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php(444): EventEspresso\core\services\assets\Registry->registerManifestFile('event-espresso-...', 'http://perfecti...', '/nas/content/st...') #1 [internal function]: EventEspresso\core\services\assets\Registry->registerManifestFiles('widgets.php') #2 /nas/content/staging/perfectimage/wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array) #3 /nas/content/staging/perfectimage/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #4 /nas/content/staging/perfectimage/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #5 /nas/content/staging/perfectimage/wp-content/plugins/mega in /nas/content/staging/perfectimage/wp-content/plugins/event-espresso-core-reg/core/services/assets/Registry.php on line 463
|
|
Josh
|
June 4, 2018 at 9:41 pm
Hi Austin,
It seems like Max Mega Menu is calling do_action on a hook that WordPress core has already fired (so code executes twice). Likely more than a few plugins will break with this unexpected chain of events. Here’s how you can avoid the Fatal error on the menus page:
1) Open up the Mega menu plugin’s megamenu.php file
2) Go to line 142, which should read as:
do_action( 'admin_enqueue_scripts', 'widgets.php' );
3) Change that line of code so it’s wrapped in a conditional:
if(!did_action( 'admin_enqueue_scripts')){
do_action('admin_enqueue_scripts', 'widgets.php');
}
4) Contact the plugin developer to see if they can add a similar check
|
|
Josh
|
June 19, 2018 at 6:56 am
Hi Austin,
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 Event Espresso you are using on the site and it should prevent the above error.
|
|
Austin Ginder
|
June 20, 2018 at 1:26 pm
New update resolves the issue. Thanks for the followup!
|
