|
lindsaywildlife
|
September 10, 2015 at 11:16 am
I’m testing out the 4.7.0 update, and the data migration is crazy slow. The site only has about 120 events and 1,415 registrations, but it says it’s trying to migrate 66,830 line items. After running the update on the server for about 4 hours, it was only at 30%.
This is a little concerning, since the site has only been up for about 6 months. In another 6 months (and on), there would be more data, and another update like this could take days. That seems insane.
Why is there so much data? Is there any way to bring the migration time down? Should I be concerned about future updates taking forever?
|
|
Lorenzo Orlando Caum
|
September 10, 2015 at 11:58 am
Hi Lindsay, it looks like most of those are probably spam/bot transactions. We now have a bot trap to reduce those from happening in Event Espresso 4.8.x.
Please cancel the migration and then restore your site from a backup.
Then please see one of our developers post here:
https://eventespresso.com/topic/split-warnings-occurred-during-your-last-migration/#post-171457
He mentions a filter that can be added to your child theme’s functions.php file which will aggressively clean up those spam / bot line items.
Allow that some time to run and then you can remove it. Then try a migration to Event Espresso 4.8.8 again and it should be much quicker.
Let us know if this helps with your migration issue.
—
Lorenzo
|
|
lindsaywildlife
|
September 10, 2015 at 12:40 pm
Thanks for the quick response, Lorenzo! I’ve rolled back to the site’s pre-update state (EE v. 4.6.25.p), and I’ve added that filter to my theme’s function. I’ve also installed Crontrol to manually trigger the cleanup process, but I don’t see any entries that might be EE’s spam cleanup? Entries are:
wp_maybe_auto_update
check_plugin_updates-eea-stripe-gateway
wp_update_plugins
wp_update_themes
wp_version_check
wp_scheduled_delete
wp_scheduled_auto_draft_delete
check_plugin_updates-event-espresso-core-reg
check_plugin_updates-ee4-events-calendar
wp_stream_auto_purge
paypalpaymentspro_renewal_cron
Thoughts?
|
|
Lorenzo Orlando Caum
|
September 10, 2015 at 1:23 pm
Hi, I had not realized that you were on 4.6.x.
The bot trap is in 4.8.x which prevents this and the clean up option that runs periodically is in 4.7.x. That combination will prevent this large number of line items once you are on the current platform for Event Espresso 4.
There is another way to get back on track by running two queries.
Are you comfortable using a tool like PHPMyAdmin?
—
Lorenzo
|
|
lindsaywildlife
|
September 10, 2015 at 1:37 pm
Yes, I can work with phpmyadmin!
|
|
Lorenzo Orlando Caum
|
September 10, 2015 at 1:58 pm
Alright, here are the steps. You’ll be working with PHPMyAdmin so begin by backing up your database.
Next, deactivate Event Espresso 4 through your WP dashboard.
Then go to your DB in PHPMyAdmin and run this query:
DELETE FROM wp_esp_transaction WHERE STS_ID = ‘TFL’ AND TXN_timestamp < '2015-09-01 00:00:00'
Then allow it to complete.
Then run this query:
delete li from wp_esp_line_item li LEFT JOIN wp_esp_transaction t ON t.TXN_ID=li.TXN_ID WHERE t.TXN_ID IS NULL
Then allow it to complete.
Afterwards, you can try the upgrade and migration again and it should move quickly for you.
—
Lorenzo
|
|
lindsaywildlife
|
September 10, 2015 at 2:10 pm
Thank you, that was a huge help! The data migration is going snappily now.
|
|
Lorenzo Orlando Caum
|
September 11, 2015 at 1:01 pm
Hello again, I was checking in to see that the migration completed and that you were able to start using Event Espresso 4.8.x.
Thanks
—
Lorenzo
|
|
lindsaywildlife
|
September 14, 2015 at 2:36 pm
Yes, the migration was able to finish and everything seemed fine with the update. Thanks again!
|
