|
EE-EGCR
|
February 5, 2024 at 4:06 pm
Performed a plugin update and it caused the website to crash with a “critical error.” I disabled EE using FTP and found the error in the server error log file (not sure if it applies now…). The version is now showing as 5.0.15p with no available updates, but I noticed the EE site shows a newer version so I deactivated and deleted EE (per online instructions), downloaded the new version, and tried to upload via the Dashboard but received a “The link you followed has expired” when I tried to install the new zip file. So now, EE is not even loaded on the site. Not sure where to go from here!
Thanks.
|
|
Tony
|
February 5, 2024 at 4:24 pm
Hi there,
Performed a plugin update and it caused the website to crash with a “critical error.” I disabled EE using FTP and found the error in the server error log file (not sure if it applies now…).
Lets start with this, what was the error?
The version is now showing as 5.0.15p with no available updates, but I noticed the EE site shows a newer version so I deactivated and deleted EE (per online instructions), downloaded the new version, and tried to upload via the Dashboard…
All good up to here 🙂
but received a “The link you followed has expired” when I tried to install the new zip file.
What that usually means is the filesize is greater than your server’s max_upload_filesize limit.
Go to Dashboard -> Media -> Add new media file.
At the bottom you’ll see “Maximum upload file size”
What value does it show?
So now, EE is not even loaded on the site. Not sure where to go from here!
First, don’t panic. We can fix this.
Do you have FTP access?
|
|
EE-EGCR
|
February 5, 2024 at 5:46 pm
Thanks for the speedy response. Following your thinking, I changed the max upload size and max post size to accommodate the file. It started processing and then threw the “There has been a critical error on this website.” message. I disabled EE via FTP and was able to access the site again. Here is the error from the server log file (note I changed my domain to “mysite”):
[06-Feb-2024 00:23:59 UTC] PHP Fatal error: Uncaught TypeError: Cannot assign int to property EE_Template_Config::$display_address_in_regform of type bool in /home/ mysite /public_html/wp-includes/functions.php:650
Stack trace:
#0 /home/ mysite /public_html/wp-includes/functions.php(650): unserialize(‘O:9:”EE_Config”…’)
#1 /home/ mysite /public_html/wp-includes/option.php(247): maybe_unserialize(‘O:9:”EE_Config”…’)
#2 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(400): get_option(‘ee_config’, Array)
#3 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(282): EE_Config->get_espresso_config()
#4 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(209): EE_Config->_load_core_config()
#5 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Config.core.php(156): EE_Config->__construct()
#6 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Dependency_Map.core.php(1004): EE_Config::instance()
#7 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Registry.core.php(795): EE_Dependency_Map::{closure}(Array)
#8 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/CoreLoader.php(110): EE_Registry->create(‘EE_Config’, Array, true, false, false, ”)
#9 /home/ mysite /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)
#10 /home/ mysite /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)
#11 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/services/loaders/Loader.php(104): EventEspresso\core\services\loaders\Loader->load(‘EE_Config’, Array)
#12 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_System.core.php(857): EventEspresso\core\services\loaders\Loader->getShared(‘EE_Config’)
#13 /home/ mysite /public_html/wp-includes/class-wp-hook.php(324): EE_System->load_core_configuration(”)
#14 /home/ mysite /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)
#15 /home/ mysite /public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#16 /home/ mysite /public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Bootstrap.core.php(47): do_action(‘AHEE__EE_Bootst…’)
#17 /home/ mysite /public_html/wp-includes/class-wp-hook.php(324): EE_Bootstrap::load_core_configuration(”)
#18 /home/ mysite /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#19 /home/ mysite /public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#20 /home/ mysite /public_html/wp-settings.php(506): do_action(‘plugins_loaded’)
#21 /home/ mysite /public_html/wp-config.php(96): require_once(‘/home/egcr/publ…’)
#22 /home/ mysite /public_html/wp-load.php(50): require_once(‘/home/egcr/publ…’)
#23 /home/ mysite /public_html/wp-blog-header.php(13): require_once(‘/home/egcr/publ…’)
#24 /home/ mysite /public_html/index.php(17): require(‘/home/egcr/publ…’)
#25 {main}
thrown in /home/ mysite /public_html/wp-includes/functions.php on line 650
You rock, Tony 🙂
|
|
Tony
|
February 6, 2024 at 9:34 am
I disabled EE via FTP and was able to access the site again.
Awesome, so I assume you’re comfortable with PHP and editing files?
Your issue is you have old config values saved which conflict with the latest type setting, but we can work around that.
Edit this file:
\wp-content\plugins\event-espresso-core\core\EE_Config.core.php
Line 2783 should be:
public bool $display_address_in_regform = true;
Change that to:
public $display_address_in_regform = true;
Then try activating EE again, does it still fatal?
(Side note, I’ll create a ticket to investigate this issue with our developers but we can troubleshoot to get EE back up and running on your site in the meantime)
|
|
EE-EGCR
|
February 6, 2024 at 1:18 pm
You are my hero, Tony. That worked! I just tried adding a new event and that worked as well. Thank you so much 🙂
|
|
Tony
|
February 6, 2024 at 3:27 pm
You’re most welcome 🙂
I’ve just pushed an update live (v5.0.17.p) which includes this fix.
|
