|
liquidflorian
|
April 9, 2018 at 8:15 pm
Hello, I’m getting the following errors migrating from 3 to 4.
Could not convert time string ’02-25-2017 16:00:00′ using timezone ‘America/Los_Angeles’ into a proper DATETIME. Using current time instead.
Could not find a ticket for old attendee with id 9764 for new event 3353, so created a new ticket with id 237
Is their a way to ignore these errors? This is mostly legacy data for us and the formatting on the pages we’ve set up, and our ability to get customers signed up for our next event, is more important than these past listings.
Thanks!
|
|
Josh
|
April 10, 2018 at 5:53 am
Hi there,
Yes you can ignore those.
|
|
liquidflorian
|
April 10, 2018 at 12:09 pm
Is their a write up or instructions on how to do that?
|
|
Tony
|
April 10, 2018 at 2:01 pm
I’m sorry but I’m not sure I follow, what is it you need instructions on how to do?
The migrations will continue on with the above errors/warnings/notices, EE is basically saying ‘I couldn’t find X so I did Y instead’, those errors are saved incase there is an issue with the migration that we need to investigate and do not prevent the migrations.
Have you ran through the migration steps and completed all migrations? They need to be run multiple times to bring all of the date up to date (the first migration works on all of the data, and then there are others that migrate much smaller sections).
What do you see on the site currently?
|
|
liquidflorian
|
April 10, 2018 at 2:28 pm
I’m getting fatal errors when ever I try and migrate the data base. I can not complete the migrations because of the above errors. The migrations stops and will not continue.
It wants me to send a large block of code to support, and it says the following:
First, check the forums to see if there is a solution before re-attempting the Database Update. Often it helps to deactivate other plugins which may have conflicts; or it may help to add
define( EE_MIGRATION_STEP_SIZE, 10 );
to your wp-config.php (which will make the update run slower, but may resolve any memory exhaustion errors.
To retry updating your data: restore to the backup you made before the update and reactivate EE (and any addons you are using) and re-run the Database Update. If you did not make a database backup and are migrating from EE3: delete your EE4 data (use the Reset/Delete Data tab above), and then reactivate EE4, and then re-run the migration and updates. If you did not make a database backup, are only updating from a previous install of EE4, have found a solution to the fatal error you received, and are willing to possibly have some data lost,
All other EE addons are disabled.
|
|
Tony
|
April 10, 2018 at 2:31 pm
I’m getting fatal errors when ever I try and migrate the data base. I can not complete the migrations because of the above errors.
The above errors aren’t the problem as they are not fatal errors but seems you are getting one somewhere during the migration.
On the page that shows the code, it wants you to send, is there not a button to email the details directly to support?
|
|
liquidflorian
|
April 10, 2018 at 2:35 pm
Yes, I’ve sent a few of these and haven’t gotten a response. I sent it again after my last comment.
|
|
Tony
|
April 10, 2018 at 2:44 pm
Hmm, strange. We aren’t getting any of those from your site (I just checked).
Can you send me login details so I can view the errors?
You can use this form: https://eventespresso.com/send-login-details/
|
|
liquidflorian
|
April 10, 2018 at 3:04 pm
Ok, it is sent. Thanks.
|
|
Tony
|
April 11, 2018 at 4:50 am
Thank you.
So the errors posted above aren’t the problem, but the only ‘real’ error logged is ‘Internal Server Error’ which isn’t the full error.
Do you have access to the server’s error logs? Your host will usually give you a section to view the error from within the control panel. If so do you see any fatal errors there?
Right now you have a few options, you can try to continue the migration and EE will pick up from wherever it can on the previous migration (some data from EE3 may not migrate over), reset the EE4 data and reattempt a full migration again (you can slow down the migration steps in case the server can’t handle the migrations), or use EE4 without the migrations.
I can provide detail on whichever step you’d like to take if you let me know how you want to proceed.
If it were me I would reset the EE4 data and attempt a migration whilst monitor the servers error logs, if you get another error you need the full error saved in the logs to then know how to prevent/fix it and continue on.
|
