|
womens-exchange
|
August 11, 2023 at 9:53 am
When I deactivate EE3 and upload EE core reg I get the above error message. I cloned the site onto a different server and was able to upload the core reg file but when I activated the plugin I never got the option to begin the Migration. I’m stuck on both and my client is waiting for the upgrade to complete.
Event Espresso version 3.1.37.18.P
WordPress version WP 6.2.2
PHP Version 7.4.10
Server Software Apache/2
Is there a way to trigger the migration?
|
|
Tony
|
August 11, 2023 at 10:29 am
Hi there,
When I deactivate EE3 and upload EE core reg I get the above error message.
Thats a WordPress error and you can get it for multiple reasons, usually it means your sever’s max_upload_size or max_post_size is too low for the upload.
One way to work around that is to upload the plugin via FTP.
Where do you want to trigger the migration currently, on the clone or the live site?
—
Lets start with the clone site as that is basically disposable currently, correct? Mean you can test the migration there and alter the database without worry as you can just reclone the site if needed.
If EE4 does not offer you the migration it means EE4 was previously installed, even if no events were created. You only see the migration option when you first activate EE4 an it detects EE3 data, if it detects anything from EE4 it assumes you made the choice of either migrating or not previously.
So what you need to do now is basically reset EE4 back to when it first activated and we have an option to do that within the database.
ON the clone site go to Event Espresso -> Maintenance ->
Go to Event Espresso -> Maintenance -> Reset/Delete Data (tab at the top)
Then click on “Permanently Delete All Event Espresso Data” button to remove all EE4 data (it doesn’t remove EE3 data).
Then reactivate EE4 and it should offer to migrate.
Test the migration on the clone site and see if all works well.
|
|
womens-exchange
|
August 11, 2023 at 1:27 pm
Thank you for the explanations of the problem and the solutions.
I ran into this issue: To put Event Espresso into Maintenance EE4 or EE5 needs to be active. When I activate EE5 Event Espresso doesn’t appear in the left panel of the dashboard so I can’t get to Maintenance. EE3 doesn’t have Maintenance as an option.
|
|
womens-exchange
|
August 11, 2023 at 2:30 pm
I have read through old posts about the issue of EE missing from the left panel of the WP dashboard. Suggestions were to copy a url to enter Maintenance Mode or reset data. I changed the url to fit my url but get a message that I’m not allowed to see that page.
Is our only option to purchase premium support to get this working? This has taken two full days and we’re no closer to getting a working plugin.
|
|
Tony
|
August 12, 2023 at 4:17 am
I have read through old posts about the issue of EE missing from the left panel of the WP dashboard. Suggestions were to copy a url to enter Maintenance Mode or reset data. I changed the url to fit my url but get a message that I’m not allowed to see that page.
Are you using this URL:
{domain}/wp-admin/admin.php?page=espresso_maintenance_settings&action=data_reset
Is our only option to purchase premium support to get this working?
I haven’t asked you to purchase a support token?
If you can send over temp login details I’ll check the above capabilities issue and see if I can reset them for you if preferred, just send them over using:
https://eventespresso.com/send-login-details/
|
|
womens-exchange
|
August 12, 2023 at 7:03 am
Thank you for your response.
“I haven’t asked you to purchase a support token?”
My apologies. I was making an assumption based on information on your support page.
“{domain}/wp-admin/admin.php?page=espresso_maintenance_settings&action=data_reset”
Yes, that is what I used. The response is: Sorry, you are not allowed to access this page.
I will send you login credentials. Thank you very much.
|
|
Tony
|
August 12, 2023 at 10:05 am
Hmm, strange. I’ve not seen the issue you are running into with 5.0.8 throwing the no access error before.
What I tried to do is install version 4.10.46 to run the migrations through that, you can then update to 5.0.8 afterwards, however, it looks like your server is missing the ctype extension from PHP.
Do you have a control panel that allows you to enable modules within your PHP settings? If no can you contact your host and ask them to enable ctype in the version of PHP that have installed?
|
|
womens-exchange
|
August 12, 2023 at 11:52 am
Thanks, Tony. I don’t know how to determine if it worked but I did enable ctype as requested. If it didn’t work let me know and I’ll ask the host to check it.
|
|
Tony
|
August 12, 2023 at 12:39 pm
Thank you, it worked.
EE4 is now activated and you work through the migration steps. Start the migration step, wait until each step is finished and keep working through each one until done.
Then update to 5.0.8 and you’ll have one more migration step to complete.
|
|
Tony
|
August 12, 2023 at 12:41 pm
Note I’ve commented out define( EE_MIGRATION_STEP_SIZE, 10 ); from your wp-config.php file.
EE will try to work out the optimum value up to 50, if you want to increase it you can set the above to something higher, if you need to decrease it use the above. BUt try without first 🙂
|
|
womens-exchange
|
August 12, 2023 at 12:48 pm
Hurray! Thank you, Tony!
Our license is EE4 Everything license. So do I have to update to 5.0.8 or will that confuse the system?
I’ll do the migration now. I can’t thank you enough for taking care of this.
|
|
womens-exchange
|
August 12, 2023 at 2:51 pm
I encountered a critical error before the first step of the migration completed. I reset EE4 data and will try again tomorrow. I am unable to locate error logs on my hosting server so I can’t tell what’s causing it to fail. I did submit a crash report to EE in case the information is of use.
Thanks for your help.
|
|
Tony
|
August 14, 2023 at 10:02 am
This reply has been marked as private.
|
|
womens-exchange
|
August 15, 2023 at 3:16 pm
Tony, thank you for all your help this weekend! Even though I messed up and the migration didn’t work we are set up with the upgraded version. Losing the old data might be a blessing in disguise. Our site size has shrunk considerably.
And thank you for activating the debug.log. That is very helpful.
***** for all your help. 🙂
|
|
Tony
|
August 15, 2023 at 4:02 pm
You’re most welcome…. but you don’t want to keep WP_DEBUG enabled all the time, yes it’s helpful but that log file can grow quickly.
Edit your wp-config.php file and set WP_DEBUG to be false, or I can do that for you if you’d like?
What you do is enable WP_DEBUG when debugging so that you can view the errors being thrown, then disable it when not. If you want errors to be logged (I recommend you do) the I’d discuss that further with your host so you can have access to log files that aren’t publicly accessible like the above are.
|
