Support

August 25, 2015 at 2:51 pm

Hello, this is fixed in Event Espresso 4.8.5:

https://eventespresso.com/wiki/ee4-changelog/

Could you cancel the migration and then restore from a backup and try again?

—
Lorenzo

August 25, 2015 at 5:49 pm

Hello again, the site enters maintenance mode when a migration process starts. However, if it did not complete then you can deactivate Event Espresso and then restore from a backup. Then upgrade to the latest version and try again.

—
Lorenzo

August 26, 2015 at 1:20 pm

Hi, thanks for checking. Please use the first option so your information is migrated.

If you use the second option, then its equivalent to starting brand new so go with the first option.

—
Lorenzo

August 27, 2015 at 1:07 pm

Hi, I let one of our developers know and he would like to take a look at your site. Could you follow up with us here?

https://eventespresso.com/send-login-details/

Please go ahead and cancel the migration and then restore from a backup so that the site is functional again. We’ll share feedback once we have had a chance to take a look at the site.

—
Lorenzo

August 28, 2015 at 10:35 am

I think from your comments above, your backup was of EE4.7.10p. So when you restore to a backup, you should also have that same version of EE active, not the current version of EE. Here is an archived copy of it that you can upload to your website: https://github.com/eventespresso/event-espresso-core/archive/4.7.10.p-sans-tests-tag.zip
You can simply deactivate what you have now, EE4.8.6.p, upload this archived version to your site, EE4.7.10.p, and activate it, and your site should be taken out of maintenance mode.

August 28, 2015 at 1:15 pm

bdearth if you visit the maintenance mode page, what does it say your site needs to be migrated FROM? Because I thought your database would be at version 4.7, and the EE4 plugin is at version 4.7, so it shouldn’t need to run any migrations or be in maintenance mode.
I suspect just visiting the maintenance mode page will force EE to realize it doesn’t need to be in maintenance mode because there are no migrations it can run

August 28, 2015 at 1:49 pm

I think the problem was that you copied the 4.7 files into the 4.8 folder. ie, you now have EE4.7 BUT IT ALSO HAS EE4.8 files in it, which is very strange.
You’d be better to delete the EE4 files, and then re-upload the zip I linked to above how you did before. That way you will be sure to have EE4.7 with absolutely no leftover files from EE4.8

September 4, 2015 at 2:37 pm

hi bdearth, I used the login credentials provided and logged into your site.
I initially found Event Espresso was still in maintenance mode but on version 4.7.10, because that version of 4.7.10 somehow had some key files from 4.8 because of how the files were copied.
In order to take Event Espresso out of maintenance mode, I followed the steps outlined https://eventespresso.com/topic/split-warnings-occurred-during-your-last-migration/#post-170526, ie, uploaded a proper copy of 4.7.10 to your site and activated it instead. I left the other polluted version on the site too in case you may want it, but it is inactive and would suggest it.
I looked in your database and you do indeed have a lot of spam transactions in your system. Our spam cleanup is working, but it’s currently quite conservative and only deletes spam transactions after a full week of being in your system.
So when you went to migrate, you’re migrating an extra 80,000 spam transactions , which explains why its taking so long.

So the solution: add this snippet of code to your functions.php file (you may need to ask a technical person; or I can do it) to make the database cleanup more aggressive and cleanup spam transactions that are a day old:

function espresso_cleanup_junk_transactions_quicker( $time_to_leave_alone ) {
return DAY_IN_SECONDS;
}
add_filter( 'FHEE__EEM_Transaction__delete_junk_transactions__time_to_leave_alone', 'espresso_cleanup_junk_transactions_quicker' );

And wait for the cleanup task to run (or manually invoke it using a plugin like Crontrol) while Event Espresso 4.7.10 is active and running. After an hour that should have cleaned most of your spam transactions, and then the migration should go by much quicker.

I’d recommend doing this when you afterwards have some time to verify everything is still running smoothly on your site. So is now a good time to re-attempt the migration?

September 4, 2015 at 3:09 pm

Ok I temporarily added that snippet and ran the cron task to clean up the spam transactions. It removed 70,000 spam transactions and their associated registrations and line items. When I upgraded to 4.8.7 and ran the migrations, they only took about 30 seconds to run. The site is now out of maintenance mode. You can now verify it’s running properly again. I’ve removed the adminer plugin and the version of 4.7.10.p I uploaded temporarily

• This reply was modified 8 years, 7 months ago by  Michael Nelson.

September 8, 2015 at 3:58 am

Hi bearth,

I just wanted to check in and see if everything is working as expected?