|
Ash
|
April 1, 2020 at 4:04 pm
We did the upgrade from Event Espresso 4.9.79.p to 4.10.5.p successfully in our staging environment
When following the same steps in the LIVE environment when we go to Event Espresso Maintenance section we can’t see the option to upgrade the database that we did when we were in the staging environment.
Is there anything we can do to show this option again?
|
|
Tony
|
April 1, 2020 at 4:11 pm
Hi there,
What do you see in the maintenance section?
Is EE in maintenance mode? (If it needs to be, EE would automatically set full maintenance mode to run migrations)
If your staging environment one that allows you to sync database changes from staging to live? If yes and you’ve pushed changes from staging to live since doing the update it might explain why you’re not getting it on live.
(Note, just to be clear, I’m not saying that’s what you should do I’m asking if that is what has already happened)
|
|
Ash
|
April 1, 2020 at 4:48 pm
Hi Tony,
In the maintenance section all I see is the ability to switch between on/off. In staging what we saw was an option to upgrade the database which we don’t see.
We did not sync staging to live so these changes I believe are not in our live database.
Is there anything we can do to show this database option again?
Or, anything we can do to check the status of the database so see if it has been updated or not?
|
|
Josh
|
April 2, 2020 at 8:58 am
You can check the status to see if it has been updated. You go into the database with a tool like phpmyadmin, then look in the wp_options table and do a search for an option that has option_name:
ee_data_migration_script_Core.4.10.0
If there’s option with that option_name along with a serialized option_value, that means the database update script was completed.
|
|
Ash
|
April 3, 2020 at 5:15 am
Hi Josh, I checked the database and the only similar option I see in the wp_options table is:
ee_data_migration_current_db_state
with a value of:
a:7:{s:4:"Core";s:8:"4.10.6.p";s:9:"Ticketing";s:8:"1.0.11.p";s:9:"MailChimp";s:7:"2.4.5.p";s:14:"Attendee_Mover";s:7:"1.0.5.p";s:10:"EE_WPUsers";s:8:"2.0.15.p";s:10:"Promotions";s:8:"1.0.15.p";s:14:"Stripe_Gateway";s:7:"1.1.8.p";}
|
|
Josh
|
April 3, 2020 at 10:03 am
That’s an indication the migration script did not run.
What you could do is backup the database, then change the ee_data_migration_current_db_state option’s Core value from this:
4.10.6.p
to this
4.9.60.p
Then go to your site’s WordPress dashboard which at that point should have a prompt to do the database update migration.
|
|
Ash
|
April 6, 2020 at 3:26 am
Perfect…this worked! thank you.
|
|
Josh
|
April 6, 2020 at 8:54 am
You’re most welcome.
|
