|
Melvin Graham
|
June 2, 2015 at 1:50 pm
I had previously used EE3 on my site. When I removed EE3 and activated EE4 none of the data carried over. Is there a way to fix this?
I previously posted here: https://eventespresso.com/topic/upgrading-from-ee3-to-ee4-migrating-database/
|
|
Lorenzo Orlando Caum
|
June 2, 2015 at 2:01 pm
Hi Melvin, what version of Event Espresso 3 were you running prior to you trying the migration?
—
Lorenzo
|
|
Melvin Graham
|
June 2, 2015 at 2:16 pm
I was using 3.1.P.9.1
I was told there was a data compatibility issue with the version and that I could try installing Event Espresso 3.1.37 Lite and see if the data was transferred over.
I installed it and could still access my data. I removed the Event Espresso 3.1.37 Lite plugin files and then installed EE4.
|
|
Melvin Graham
|
June 2, 2015 at 2:21 pm
I also got this notification after installing EE4:
Event Espresso recommends PHP version 5.4.33 or greater for optimal performance. You are currently running version 5.3.13.
In order to update your version of PHP, you will need to contact your current hosting provider.
|
|
Josh
|
June 2, 2015 at 4:15 pm
When you activated Event Espresso 4 for the first time, was there a notification that prompted you to run the migration?
|
|
Melvin Graham
|
June 2, 2015 at 4:19 pm
No prompt. It did take about 5 minutes for the plugin to activate.
|
|
Tony
|
June 3, 2015 at 5:32 am
Hi Melvin,
So currently if you hover over the Event Espresso top level menu, what do you see? Like this – http://take.ms/imlWx
It will not match exactly, but do you see multiple different menus like that or only a few links?
|
|
Tony
|
June 3, 2015 at 5:33 am
Also in your previous thread, did you activate EE4 at any time before updating to 3.1.37.L?
|
|
Melvin Graham
|
June 3, 2015 at 8:29 am
Yes, I see the menu like the screenshot you provided.
Yes, I did activate EE4 before updating to 3.1.37.L
Thanks!
|
|
Tony
|
June 3, 2015 at 9:30 am
Ok, so the reason the migrations aren’t running is because they are only ran on the initial install, so because EE4 was activated before you updated to 3.1.37, EE4 checked to see if it could run migrations, it could not and update the EE4 settings.
Now, even though you have updated your EE3 data, the option for migrating EE4 has already been updated, so migrations are skipped… does that all make sense?
We have a solution for this, EE4 has built in functions to complete wipe your EE4 data and start from scratch. However, before doing this can you confirm you have a full site backup (including all files and the database)?
The most important backup is the database, so at the very least you must create a backup before continuing, there are many ways to do this, heres a plugin I use:
https://wordpress.org/plugins/backupwordpress/
But you can use any method you prefer.
|
|
Melvin Graham
|
June 3, 2015 at 10:32 am
I’ve got everything backed up. Can you post next steps?
|
|
Tony
|
June 3, 2015 at 10:35 am
Go to Event Espresso -> Maintenance -> Reset/Delete Data.
Click ‘Permanently Delete All Event Espresso Data’ – http://take.ms/MWkeZ
This will remove ALL of your EE4 data and disable the plugin (it will be as if EE4 had never been activated)
Re-activate EE4 and the migrations should run.
|
|
Melvin Graham
|
June 3, 2015 at 2:00 pm
I followed your instructions and got this error after re-activating the plugin:
[Incorrect key file for table ‘/mysql-tmp/#sql_c50_1.MYI’; try to repair it] SHOW FULL COLUMNS FROM wp_options
database error: [Incorrect key file for table ‘/mysql-tmp/#sql_c50_1.MYI’; try to repair it] SHOW FULL COLUMNS FROM wp_options
I got the prompt to migrate data and click on it. I began the first part of the migration process. It started and gave me this error:
A Fatal Error Has Occurred
WordPress database error: [Incorrect key file for table ‘/mysql-tmp/#sql_c50_1.MYI’; try to repair it]
SHOW FULL COLUMNS FROM wp_options
{“error”:false,”success”:false,”notices”:”
<\/div>”,”content”:””,”data”:{“records_to_migrate”:0,”records_migrated”:0,”status”:”status_fatal_error”,”message”:”Unknown fatal error occurred: The error ‘Incorrect key file for table ‘\/mysql-tmp\/#sql_c50_1.MYI’; try to repair it’ occurred updating the status of the migration. This is a FATAL ERROR, but the error is preventing the system from remembering that. Please contact event espresso support.
\n\t\t\t
WordPress database error:<\/strong> [Incorrect key file for table ‘\/mysql-tmp\/#sql_c50_1.MYI’; try to repair it]
\n\t\t\tSHOW FULL COLUMNS FROM wp_options<\/code><\/p>\n\t\t\t<\/div>
\n\t\t\t
WordPress database error:<\/strong> [Incorrect key file for table ‘\/mysql-tmp\/#sql_c50_1.MYI’; try to repair it]
\n\t\t\tSHOW FULL COLUMNS FROM wp_options<\/code><\/p>\n\t\t\t<\/div>”,”script”:”Unknown”,”template_args”:{“admin_page_header”:””,”admin_page_content”:””,”post_body_content”:””,”before_list_table”:””,”after_list_table”:””,”notices”:”
<\/div>”}},”isEEajax”:true}
Migrated 55 records successfully during Organization Options/Config
I pressed the next button to continue the migration and then got sent to the crash report page, which I sent to you all. I pressed the button to attempt to continue the database transfer and it opened a blank screen with this error:
Fatal error: [] operator not supported for strings in /hermes/bosnaweb02a/b2284/ipg.kiecocenterorg/msdc/wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Class_Base.core.php on line 147
|
|
Tony
|
June 3, 2015 at 2:34 pm
This error:
[Incorrect key file for table ‘/mysql-tmp/#sql_c50_1.MYI’; try to repair it] SHOW FULL COLUMNS FROM wp_options
database error: [Incorrect key file for table ‘/mysql-tmp/#sql_c50_1.MYI’; try to repair it] SHOW FULL COLUMNS FROM wp_options
Looks like mySQL is attempting to create a temporary file and it can’t. Temp files are used when your are running large queries.
Can you issue a ticket with your hosting company and have them check this please? Either you are running out of disc space or mysql is unable to create the temporary file.
More information can be found here:
http://stackoverflow.com/questions/2011050/mysql-126-incorrect-key-file-for-table
With a possible solution here:
http://stackoverflow.com/questions/19003106/mysql-error-126-incorrect-key-file-for-table
|
