|
Ryan DesRoches
|
May 15, 2015 at 7:50 pm
I’m trying to make the update from EE3.1.37.3.P to EE4.6.27.p – I luckily backed up my database before starting!
Anyway – when I activate EE4 and start the migration process, on the first step I get a lot of warnings (see below) but no errors. When I “finish” the process and get to EE4.6 – the maintenance tool makes it seem that everything went ok.
When I check the data though – I only show about 39 total registrations, where I should have over 700! Some of my events that had 40+ registrations are now showing 0, and I’m not sure why.
I would really love to update to EE4 to take advantage of some features, but I can’t seem to get the data over.
Here is a dump of those warnings:
redacted – Event Espresso support team – LOC
Help is appreciated!
|
|
Lorenzo Orlando Caum
|
May 18, 2015 at 1:16 pm
Hi Ryan, I removed the warnings log since our support forums are partially public and shared that information with a developer.
I’ll update this support post once I have more information.
Thanks
—
Lorenzo
|
|
Lorenzo Orlando Caum
|
May 18, 2015 at 6:29 pm
Hello again, could you also let us know the version of WordPress that is in use?
Was this 4.2.2?
Thanks
—
Lorenzo
|
|
Ryan DesRoches
|
May 18, 2015 at 8:13 pm
Thanks for the reply. Yes, its WordPress 4.2.2 running on Network Solutions host. The latest version of PhP is also installed.
|
|
Lorenzo Orlando Caum
|
May 19, 2015 at 8:07 am
Thanks, I’ve added your feedback to the current ticket that our developers are reviewing.
—
Lorenzo
|
|
Ryan DesRoches
|
June 4, 2015 at 6:44 pm
Have we got any feedback from the developers on what the issue might be?
|
|
Dean
|
June 5, 2015 at 1:50 am
Hi,
This should have been included in the 4.6.29 update, have you updated your version of EE4 to the latest?
|
|
Ryan DesRoches
|
June 16, 2015 at 7:05 pm
Hi All, I just tried the update again from the latest version of EE3 (Version 3.1.37.4.P) to EE4 4.7.1P and still got a ton of warnings on the first DB migration (similar to the log I sent in original message).
I am also getting errors like this:
Database table wp_esp_ticket existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? 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 wp_esp_ticket. 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 wp_esp_ticket manually then restore to the backup again.
Dismiss
Database table wp_esp_ticket_price existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? 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 wp_esp_ticket_price. 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 wp_esp_ticket_price manually then restore to the backup again.
However, it does seem a little better than before – however, I did restore my backup of the DB to the EE3 version because of the warnings. Any idea of what might be causing these?
|
|
Ryan DesRoches
|
June 16, 2015 at 7:32 pm
Note, that most of these warnings occur in the first step of the migration process.
I am running MySQL5 on Network Solutions if that helps.
|
|
Josh
|
June 17, 2015 at 7:37 am
The way forward is to (1) remove all the EE4 data but leave all the EE3 data in place, and then (2) re-migrate your data from EE3.
To do (1), you go to EE4’s maintenance page, click the “Reset/Delete Data” tab (which is accessible while Event Espresso is in maintenance mode too), and then click “Permanently Delete All Event Espresso Data”. The button should really be labelled “Permanently Delete All Event Espresso 4 Data” (there isn’t yet an option to delete EE3 tables). This will delete all your EE4 tables, data and wp options but it will leave your EE3 tables, data and options in-place, and it will deactivate EE4 for you.
To do (2), you re-activate EE 4.7.1.p and run the migrations.
|
|
Ryan DesRoches
|
June 17, 2015 at 7:54 am
Thanks Josh, I will try this step on Friday which is our next chance to do the upgrade.
I’ll let you know how it goes.
|
|
Ryan DesRoches
|
June 25, 2015 at 6:46 pm
Thanks for all the help. We finally upgraded and verified no data loss. We are still working out some issues with the emails not being sent all the time, but I think we can close out this issue.
Thanks
ryan
|
|
Josh
|
June 26, 2015 at 6:11 am
Thanks for the update, glad to hear the data migration went well.
|
