Posted: August 12, 2024 at 10:23 am
I have Event Espresso 5.0.22.p installed and when ever I enable it it crashes my sit. Even with debugging enabled it shows generic critical error. So it is currently disabled. https://www.themeadowssarasota.org/mca-events/ WP stats/info below: Server architecture Linux 4.18.0-553.8.1.lve.el8.x86_64 x86_64 |
|
I’ve also deactivated all other plugins, tried re-uploading the newest version downloaded from my Event Espresso account. I even tried activating Twenty Twenty-Four 1.2 theme and still no go. Just shows “There has been a critical error on this website.” |
|
Hi there, “There has been a critical error on this website.” Is the ‘pretty’ version of a fatal error, to know what the issue is here we’ll need the ‘full’ error. If you check the server’s PHP error logs is should show your the full error including a stack trace there, can you post that here? Your host will usually have a section for you to view server errors in your control panel, if not yu can add this to your sites wp-config.php file: https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug That tells your site to store errors in /wp-content/debug.log so the error should show up there. |
|
I am having the same issue. This is the error message I have: An error of type E_ERROR was caused in line 123 of the file /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/domain/entities/config/legacy/EE_Admin_Config.php. Error message: Uncaught TypeError: EE_Admin_Config::useAdvancedEditor(): Return value must be of type bool, null returned in /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/domain/entities/config/legacy/EE_Admin_Config.php:123 Stack trace: #0 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/domain/entities/config/legacy/EE_Config_Base.php(66): EE_Admin_Config->useAdvancedEditor() #1 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(258): EE_Config_Base->populate() #2 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(144): EE_Config->_load_core_config() #3 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(82): EE_Config->__construct() #4 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1050): EE_Config::instance() #5 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(754): EE_Dependency_Map::{closure}(Array) #6 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/CoreLoader.php(109): EE_Registry->create(‘EE_Config’, Array, true, false, false, ”) #7 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/CachingLoader.php(157): EventEspresso\core\services\loaders\CoreLoader->load(‘EE_Config’, Array, true) #8 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/Loader.php(81): EventEspresso\core\services\loaders\CachingLoader->load(‘EE_Config’, Array, true) #9 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/Loader.php(104): EventEspresso\core\services\loaders\Loader->load(‘EE_Config’, Array) #10 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(843): EventEspresso\core\services\loaders\Loader->getShared(‘EE_Config’) #11 /home4/nsaausti/public_html/wp-includes/class-wp-hook.php(324): EE_System->load_core_configuration(”) #12 /home4/nsaausti/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #13 /home4/nsaausti/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #14 /home4/nsaausti/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Bootstrap.core.php(47): do_action(‘AHEE__EE_Bootst…’) #15 /home4/nsaausti/public_html/wp-includes/class-wp-hook.php(324): EE_Bootstrap::load_core_configuration(”) #16 /home4/nsaausti/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #17 /home4/nsaausti/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #18 /home4/nsaausti/public_html/wp-settings.php(555): do_action(‘plugins_loaded’) #19 /home4/nsaausti/public_html/wp-config.php(107): require_once(‘/home4/nsaausti…’) #20 /home4/nsaausti/public_html/wp-load.php(50): require_once(‘/home4/nsaausti…’) #21 /home4/nsaausti/public_html/wp-admin/admin.php(34): require_once(‘/home4/nsaausti…’) #22 {main} thrown |
|
i’m having the same issue |
|
When I enable the plugin and it errors, The below is the most reent logs shown. 2024-08-08 06:50:56.473196 [NOTICE] [2132416] [T0] [69.171.230.10:62064:HTTP2-1#APVH_themeadowssarasota.org:443] [STDERR] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home/themeado/public_html/wp-includes/plugin.php on line 203\n 2024-08-08 06:50:56.472462 [NOTICE] [2132416] [T0] [69.171.230.10:62064:HTTP2-1#APVH_themeadowssarasota.org:443] [STDERR] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home/themeado/public_html/wp-includes/class-wp-fatal-error-handler.php on line 76\n |
|
php error log results here: [12-Aug-2024 19:40:02 UTC] PHP Fatal error: Uncaught TypeError: EE_Admin_Config::useAdvancedEditor(): Return value must be of type bool, null returned in /home/themeado/public_html/wp-content/plugins/event-espresso-core-reg/core/domain/entities/config/legacy/EE_Admin_Config.php:123 |
|
Same here: apfmnet.org. PHP 8.1. Divi theme. |
|
Hi all, I’ve just pushed 5.0.23.p live specifically to fix the error posted above. Can you please update to the latest version and try again. You’ll likely need to update EE manually as you can’t activate it to update through the one-click method. Download 5.0.23.p from your account page and save the .zip somewhere. On the site go to Dashboard -> Plugin -> Add new plugin -> Upload plugin. When you upload the .zip you downloaded above, if you haven’t renamed the directory of the version of EE installed on your your site then WordPress will show a message stating it already exists ask if you want to replace it, do so. Now you’ll have 5.0.23.p installed, activate it. If anyone still has an error with that version I’ll need to take a deeper look, for that I’ll need WP Admin and FTP credentials which you can send over using this form: |
|
Worked for me. Thank you so much! |
|
Awesome I’m glad it worked for you. Any further issues just let me know. —-
It depends on many factors, its not just Event Espresso but a combination of all the plugins on the site (EE can show the error but that just means EE’s processing tipped it over the edge). generally what you have available based on the error messages is ‘usually’ enough. However, what stands out right now is the bytes in the error conflicts with what you posted. The error:
134217728 bytes is roughly 134MB. You’re not hitting a limit of 512MB but hitting 128MB, likely with some wiggle room (which is why it shows 134MB). The above version should prevent the fatal if your running into the same reason for the error, but you’ll need to investigate why the server is limiting your site to 128MB if you’ve set the PHP memory_limit value to be 512MB. |
|
Thank you for the quick responses Tony. Version 5.0.23.p seems to be working as it should on my site. I’ll let you know if I run into further issues. |
|
Awesome. If you need anything, feel free to let us know. thanks |
|
5.0.23.p seems to be working as it should on my site as well |
|
Please feel free to create a new ticket if you have any other questions. |
|
Great! Any further issues just let us know. |
|
The support post ‘Event Espresso 5.0.22.p crashes my site’ 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.