|
homehouse
|
April 3, 2019 at 8:03 am
Hi, I have the latest version of EE installed but it is stuck in maintenance mode saying that I need to update the DB. When I click the button to continue the database update its just stuck at 21% and then results in a fatal error. So the plugin is completely broken atm and I can’t seem to fix it. I’ve tried adding define( ‘EE_MIGRATION_STEP_SIZE’, 10 ); to the wp-config file and this has made no difference at all.
|
|
Josh
|
April 3, 2019 at 11:43 am
Hi,
Have you checked the server’s PHP error log to find the fatal error?
|
|
homehouse
|
April 4, 2019 at 2:49 am
Hi,
I have and this is the fatal error message I am receiving.
[client 127.0.0.1:64246] PHP Fatal error: Uncaught EE_Error: Event Espresso Level 2 Maintenance mode is active. That means EE can not run ANY database queries until the necessary migration scripts have run which will take EE out of maintenance mode level 2. Please inform support of this error. in /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:2289\nStack trace:\n#0 /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(992): EEM_Base->_do_wpdb_query(‘get_results’, Array)\n#1 /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(866): EEM_Base->_get_all_wpdb_results(Array, ‘ARRAY_A’, NULL)\n#2 /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(1178): EEM_Base->get_all(Array)\n#3 /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(1122): EEM_Base->get_one(Array)\n#4 /nas/content/liv in /nas/content/live/homehousenew/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2289
|
|
Josh
|
April 4, 2019 at 7:09 am
Hi,
We received your request for priority support. Since this is a live site hosted on WPEngine, I can advise to restore the site to the backup point just before the update was attempted. Then, you can use WPEngine’s staging site feature to spin up a staging site.
Once the staging site is set up, you can resend the details for priority support to include the staging site access information. If possible, please also send credentials for accessing the database.
|
|
homehouse
|
April 4, 2019 at 9:57 am
This reply has been marked as private.
|
|
Josh
|
April 4, 2019 at 6:00 pm
Someone from your team already had sent details.
Anyway, the reason the fatal error happened was because the software versions were switched up and down between major versions. You’ll see a few examples in this screenshot of the site’s version history for EE:
https://slack-files.com/T02SY781D-FHPSND7NK-59d2e8f0f2
So in the wordpress options table, there was an option that recorded the result of an older version of EE 4.8 that ran its migration a few years ago (2016). Migrations to a major version can and only should be run once.
Once that option was edited in the database the migration could be completed.
Going forward, you can avoid getting into a situation like this one by using WPEngine’s staging feature where these things can be worked out ahead of time.
|
