|
Elizabeth
|
June 6, 2016 at 8:08 pm
I ran the update from EE3 to EE4 and get 10 of these:
Database table mm_esp_country exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from mm_esp_country. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from mm_esp_country manually then restore to the backup again.
Database table mm_esp_datetime exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from mm_esp_datetime. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from mm_esp_datetime manually then restore to the backup again.
Database table mm_esp_event_meta exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from mm_esp_event_meta. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from mm_esp_event_meta manually then restore to the backup again.
|
|
Elizabeth
|
June 7, 2016 at 12:06 pm
Any word on this? Happened on 3 sites. Thanks
|
|
Tony
|
June 7, 2016 at 4:18 pm
Are these sites part of a multisite network or single site installs?
Had these sites ever had EE4 activated on the before the migration at all?
If you look within Event Espresso -> Maintenance -> System information
Look for ‘ee_activation_history’ and see which version numbers are shown there.
|
|
Elizabeth
|
June 8, 2016 at 3:49 pm
Single site
I followed the steps given by EE. I disabled all EE3 plugins, installed EE4, activated, then went through upgrade process.
ee_activation_history
3.1.36.4.P
unknown-date
3.1.36.5.P
unknown-date
3.1.37.1.P
unknown-date
3.1.37.3.P
unknown-date
3.1.37.4.P
unknown-date
3.1.37.5.P
unknown-date
3.1.37.6.P
unknown-date
3.1.37.7.P
unknown-date
3.1.37.8.P
unknown-date
4.8.43.p
2016-06-06 23:24:04
|
|
Tony
|
June 9, 2016 at 2:38 am
Hmm, so that activation history is fine.
If you can create a test event within EE you can safely dismiss those messages.
Basically EE checks the database for any current tables and compares those with the tables that it ‘should’ have. Somehow along the way the function that checks those tables has thrown a warning to say the tables already existed.
I’ll check in with our developers on this but if you dismiss the messages you should not have any problems.
|
|
Elizabeth
|
June 9, 2016 at 1:41 pm
I’ll try it, but have you seen that error before?
Did you check with the developers?
|
|
Tony
|
June 9, 2016 at 2:47 pm
We have seen this before, but not straight from a migration.
I did check with the developers and if you have never installed EE4 previously and have never installed EE4 then reverted to a backup (leaving some of the EE tables within the database) then the notices are false and can be dismissed.
Is this a development site or live and are you currently taking registrations on the site?
We made some changes in 4.9 that should prevent those notices from happening when you run the migrations, however to confirm that you would need to migrate from EE3 on the site once again.
|
|
Elizabeth
|
June 9, 2016 at 3:14 pm
Right now it is in development. How would I migrate it again?
|
|
Josh
|
June 9, 2016 at 3:27 pm
You’d start with a database backup from before the migration was run.
|
|
Elizabeth
|
June 9, 2016 at 3:58 pm
so restore then update to 4.9, then run update?
|
|
Tony
|
June 10, 2016 at 1:57 am
Yes, restore the site back to before you activated EE4.
Install EE4.9 and run the migration.
|
