|
Nicolas Alberto
|
November 13, 2019 at 12:43 am
It looks like WP 5.3 introduces bug fixes for datetime functions. Unfortunately this breaks all the datetime in EE 3
Short terms fix for us is the set the WP timezone to London time even though we are in Australia.
It looks like this could be a major bug that will affect many sites upgrading to WP 5.3
To replicate, have the timezone of youp wp site to anything not like london. Set you even start time and end time in backend. On applying the changes you will see that the date stored do not match and same in event listing and registration page.
|
|
Josh
|
November 13, 2019 at 6:23 am
Hi,
Feel free to download and install this branch of 3.1.37.15.P that includes a fix:
https://github.com/eventespresso/event-espresso-legacy/archive/BUG/wp53-datetimes.zip
Or, you could alternatively migrate to EE4 where this isn’t an issue.
|
|
Nicolas Alberto
|
November 13, 2019 at 7:09 pm
I would love to migrate to EE4 but we have been waiting 4 years for recurring event module…
I will try the patch
|
|
Josh
|
November 14, 2019 at 11:06 am
Update:
The fix is included in the latest release of EE3. Event Espresso 3.1.37.15.P. It’s available to download from your account page.
|
|
Erik
|
November 18, 2019 at 7:45 pm
This reply has been marked as private.
|
|
Josh
|
November 19, 2019 at 5:38 am
Hi Erik,
1) Download the latest release of the EE3 plugin from GitHub
2) Go to your WP Dashboard Plugins page and deactivate and delete the lite version of Event Espresso (you will not lose data because Event Espresso does not run uninstall scripts when you deactivate & delete the plugin)
3) Upload the new plugin to your site via Dashboard -> Plugins -> Add New.
4) Activate the plugin.
|
|
Erik
|
November 19, 2019 at 12:20 pm
Hi Josh,
You’re the best, that worked. Thank you very much.
Hopefully it won’t be too much longer before we are using EE4. I have confidence that the people we are working with to create our new website and who are doing the migration from EE3 to EE4 should all work out but just incase you guys do have the ability to pay for a support token or something like that if a problem arises, correct?
I figured I would ask now, if there was an option still available, to pay for additional assistance if something does come up.
Again, thank you. You guys have always been great.
Erik
|
|
Tony
|
November 20, 2019 at 2:26 am
Hi Erik,
It is difficult for us to say ‘we can help with migrations’ as there is a vast number strange things we’ve seen people do in EE3 that simply can not be applied to EE4 and/or migrated over without a significant amount of development time (which a support token wouldn’t cover).
Will we help if we can? Of course! But we need to assess each migration and go from there. If something you have in EE3 is going to take a lot of debugging on our part because it’s not ‘standard’ then we need to cover that time with support tokens which can mount up depending on the circumstances.
I want to be clear that I’m not saying you’re on your own with migrations, generally, they go through without a problem and the most common issues are from the site running out of memory or another plugin interfering which are simple fixes (increase the memory available and/or disable the other plugins on the site when running the migrations). I just think it’s important to let you know early on that migrations can be tricky depending on how EE3 has been used and it depends how much time/resources you want to put into a tricky migration (if you have one) as opposed to starting fresh and just keeping an ‘archive’ site with your old registration/event data if needed.
|
|
Erik
|
November 20, 2019 at 7:04 am
Thank you Tony for the follow up. I don’t think there will be any serious migration issues, or I hope not. I have had a pretty successful trial run when I performed the migration on a localhost setup myself. Most of the errors seemed to be minor and may be fixable prior to migration or even after. Plus I have help this time and the developer has had experience with EE.
I was hoping if we do have to reach out to you guys for extra support, it will be to address a specific error or issue with the migration and not with the complete migration from start to end. But I completely understand your explanation.
I appreciate all the help and the detailed answers you guys provided.
Thanks,
Erik
|
|
Tony
|
November 20, 2019 at 7:34 am
Something to note with EE4 migrations is we post a lot of ‘notices/warnings’ during the migration, and a lot of which are non-critical, for example:
‘Couldn’t find attendee with ID X, so we created a new one’
‘Payment Y doesn’t match a valid payment method, so marking as “unknown”‘
So not all ‘errors’ are actual errors and need a fix at all 🙂
We have to post the details to keep you (the admin performing the migration) informed and so we can save the output into a migration report to send to us (if needed).
I was hoping if we do have to reach out to you guys for extra support, it will be to address a specific error or issue with the migration and not with the complete migration from start to end.
I’ll give you an example of something we’ve had in the past so you know what I’m referring to.
We’ve had users ‘repurpose’ one of the EE3 system questions (one of the address questions and IIRC it was city and will use that but either way it was a system question intended to be used for something specific, that’s why they are system question) for use as DOB on the registration form.
EE4 took that info from EE4 and migrated every instance of that question into what it should have been used for in EE4, city. Now EE4 is full of ‘cities’ that are DOB answer, so for example city 12/12/2005.
Fixing that before the migration is complex as all of your registrant data now uses the city as DOB so every attendee would need to be updated, or ignored, or wiped so the migration had no value (note the multiple possible fixes).
Could we fix it? Sure! But that certainly not within the timeframe of 1 (or 2/3 support tokens) so it’s then a question how important the data is and if it’s worth the migration etc.
—
As mentioned, the majority of migrations go through smoothly with maybe the odd error which is easily fixed so please do let us know if you run into problems.
Open a thread here and provide some details of what is happening, we can run through some steps to try first and it still doesn’t work look into possibly using a support token etc.
|
