|
Manuel
|
June 26, 2024 at 3:03 am
Two days ago I updated to the latest version of Event Espresso, and unfortunately I see 2 problems.
There is a new registration (or update) status “Not approved / Awaiting Review”. However there seems no translation for it. I already updated and synchronised the translation file, but cannot find this entry. See screenshot: https://pevaz.be/wp-content/uploads/2024-06-26_10h53_23.png
Second problem is that there seems to be an update on the date field. See screenshot 2: https://pevaz.be/wp-content/uploads/2024-06-26_11h00_17.png. There is no problem for new entries, but since I have hundreds of existing registration in the database with the existing date field, you cannot see the originally entered date anymore. When I do an export of the registrations, I still see the originally entered birthdate, but when you edit the existing registration the field is show as in the screenshot. It seems that there is no entry.
The main problem in this case is also that if you update another field, the originally entered date vanishes.
Thank you for the quick bugfix.
|
|
Tony
|
June 26, 2024 at 9:33 am
Hi there,
There is a new registration (or update) status “Not approved / Awaiting Review”. However there seems no translation for it. I already updated and synchronised the translation file, but cannot find this entry. See screenshot: https://pevaz.be/wp-content/uploads/2024-06-26_10h53_23.png
I’ve just updated our translations to make sure they are up to date.
Can you pull in the latest translation file from here:
https://translate.eventespresso.com/projects/event-espresso-4/
And let me know if that fixes it for you.
Second problem is that there seems to be an update on the date field…..
This I am currently investigating and will get back to you once we know more.
|
|
Manuel
|
June 26, 2024 at 12:15 pm
Hello Tony
Thank you for your reply. I use Loco translate for translations of the file. However when I synchronise the file, it is not updated. I can obviously download the file from the repository above, but the problem is that this file is only translated for 79%. In the years that I use Event Espresso I have translated a lot of extra’s. I have a translation ratio of 97% 🙂 If you want I can always share my dutch translation file.
Thank you for the update on the date field.
|
|
Tony
|
June 26, 2024 at 12:48 pm
I can obviously download the file from the repository above, but the problem is that this file is only translated for 79%
Earlier today the file was 99% translated, it’s now 79% because of new strings or amendments.
What file do you need to be able to update within Loco?
The latest POT file?
If you just update your current PO file with all of the latest changes within EE from the POT file you’ll find it will also drop to somewhere around 80%
Download it locally and test there using POEdit, you’ll see 🙂
I can sent you the POT file if you prefer to use that (A POT file is simply an empty translation file, it has all of the original strings and 0 translations, POEdit/Loco/Etc just read those strings and add/update them to your PO)
|
|
Manuel
|
June 27, 2024 at 7:10 am
Hello Tony, Loco translate automatically loads the latest version of the file. I do see that it updates to the version of yesterday, but also in this PO version only there is no translation string for “Not approved / Awaiting Review”. Is it possible that you forget this string in the uploaded file?
|
|
Tony
|
June 27, 2024 at 7:38 am
Loco translate automatically loads the latest version of the file.
What file? Where is Loco pulling the file from?
I do see that it updates to the version of yesterday, but also in this PO version only there is no translation string for “Not approved / Awaiting Review”
From where? GlotPress?
You manually updated to the version I sent you? Locotranslate will not automatically pull in that file.
Is it possible that you forget this string in the uploaded file?
Nope, its there 🙂
https://monosnap.com/file/wHRQ9zHun12sysi9Inq0L2nzjbrkI5
Thats just from me download the PO file from the GlotPress project and searching it within POEdit.
|
|
Manuel
|
June 27, 2024 at 9:56 am
Hello Tony, thanks for your help. I think it was a caching problem at my side. I have manually downloaded the PO file and now it’s ok.
Would you already have an update on the second problem concerning the new date format?
|
|
Tony
|
June 27, 2024 at 4:42 pm
Hello Tony, thanks for your help. I think it was a caching problem at my side. I have manually downloaded the PO file and now it’s ok.
Awesome! I’m glad it worked.
Would you already have an update on the second problem concerning the new date format?
We’ve found the issue causing it and currently working on a fix, as long as no issues are found from that fix we’ll push an update to fix this on Monday.
|
|
Manuel
|
June 29, 2024 at 4:42 am
Thank you. Looking forward to the fix.
|
|
Manuel
|
July 8, 2024 at 8:52 am
Hello Tony, is there an update on the fix? I didn’t see any updates, and the issue is still there. I really need an urgent fix, since I need now to manually update the birthdates of every participant when I need to change something about there registration. This is really time consuming since I first need to export data to a csv, lookup there current date, …
|
|
Sam
|
July 8, 2024 at 11:59 am
Hi Manuel,
As I can see, the issue is already fixed as a high-priority task and will be added to the plugin as soon as possible.
|
|
Manuel
|
July 16, 2024 at 12:57 pm
Hello, Is there an update on the new version with the bug fix please. The client keeps struggling with this, since he already lost different birthdates.
|
|
Tony
|
July 16, 2024 at 4:27 pm
Hi there
The fix for this has been included within 5.0.21.p which has now been released.
If you don’t see the update available on your site just yet then go to Dashboard -> Event Espresso -> General Settings.
Make no changes and just hit save to force an update check.
Then go to Dashboard -> plugins and the update should show for Event Espresso there.
|
|
Manuel
|
July 17, 2024 at 6:16 am
Thank you. I have downloaded the update.
|
|
Tony
|
July 17, 2024 at 6:37 am
You’re most welcome, any issues just let me know.
|
|
Manuel
|
July 24, 2024 at 9:15 am
Hello Tony, unfortunately the problem is still not resolved. When I update existing reservations, I still cannot see the birthdates in the form. However when I export the data to csv, I can see the dates. So it is in the database, but since the update of 5.0.19 the dates are not shown anymore. It just shows dd/mm/yyyy
|
|
Sam
|
July 24, 2024 at 11:01 am
Hi Manuel,
I’ve checked the same with 5.0.21 and can see everything is fine on my end.
Is the issue happening with old events only or on the new events as well?
Can you please share the https://eventespresso.com/send-login-details/ so that we can check?
|
|
Manuel
|
July 24, 2024 at 11:20 am
What do you mean with old events? I have this issue with all events that has been created before the update to version 5.0.20p. With new events that has been created since version 5.0.20 I have now issues and I see the birthdates.
Since I have hundred of registrations, I really cannot lose the birthdates. Since I need them for insurrance papers.
|
|
Tony
|
July 24, 2024 at 1:44 pm
Hmmm, strange.
5.0.21 fixes the Datetime input issue for me.
What date format is the site set to use?
Can I log in to take a look what is happening on the page?
|
|
Manuel
|
July 25, 2024 at 5:40 am
The date format is set to belgium (dd/mm/jjjj). In a private message, I will sent you an account that you can login to the site.
|
|
Tony
|
July 25, 2024 at 5:42 am
You can send login cred over using this form rather than a private reply:
https://eventespresso.com/send-login-details/
|
|
Manuel
|
July 25, 2024 at 5:52 am
This reply has been marked as private.
|
|
Manuel
|
July 30, 2024 at 3:33 am
This reply has been marked as private.
|
|
Rio
|
August 20, 2024 at 8:08 pm
Sorry to update this thread late.
We have EE update, have you tried if this issue is still existed on our latest update?
thanks
|
|
Manuel
|
August 21, 2024 at 1:17 am
Hello Rio, I have just updated to the latest version, but unfortunately the issue is still not resolved! As in the example above, the issue still exists!
|
|
Rio
|
August 21, 2024 at 5:51 am
This reply has been marked as private.
|
|
Manuel
|
August 21, 2024 at 5:58 am
yes, no problem
|
|
Rio
|
August 21, 2024 at 6:09 am
Awesome.. We will keep you updated with our testing and plugin update.
thanks
|
|
Rio
|
August 21, 2024 at 6:11 am
Before we can do that, Can you update our Role to Admin. So we can install plugin and create Backup?
thanks
|
|
Manuel
|
August 21, 2024 at 6:28 am
The role has been changed to admin
|
|
Rio
|
August 21, 2024 at 6:35 am
Awesome, We will keep you updated with our debugging and plugin update.
thanks
|
|
Tony
|
August 21, 2024 at 9:25 am
Hi Manuel,
Have you changed the date format in use on the site?
The problem you are running into right now is the date for that registration can be interpreted in different ways…. I’ll give you an example using a different value.
31/07/1975
Logically when we look at that value, we know it’s 31st of July, 1975.
However, PHP can’t work that out on its own and needs to know the date format its in, if we don’t pass a format PHP interprets ambiguous formats in the following ways:
/ separators may be interpreted as the American format m/d/Y, so 06/01/2000 will be parsed as June 1, 2000
- separators may be interpreted as the European format d-m-Y, so 06-01-2000 will be parsed as Jan 6, 2000
Knowing that, you can see that PHP is going to use 31/07/1975 as m/d/Y, 31st month isn’t valid and returns false when mean you see the dd/mm/yyyy placeholder.
—
Earlier on I asked what your sites date format is and you replied with:
The date format is set to belgium (dd/mm/jjjj).
But if that was/is the case then the new code we added to fix the datepicker input would have been able to work out the format, so has this changed? (I can see its not set to use that format currently).
To explain, what we do now is pull the value in form the Database and first try to process the value using the sites current date format (which with the date for that user and your current date format, will fail), then if that fails we try to process the date allowing PHP to work out the date (which, based on the above for this example will again fail) and eventually if all of that fails we return the original value set in the data (which is happening on your site but the date picker can’t process it… based on the format again.
|
