amweb
Forum Replies Created
-
Posts
-
Hello again,
May I kindly ask for an update on this?
The concerned visitors are starting to get really angry and their anger is getting quite contagious… So ignoring the issue and sweeping it under the carpet is really not a valid approach (even if we all know that IE sucks and nobody has even the slightest will to look into its buggy behaviour).
I thank you in advance for your feedback, hoping that I will not have to wait again for almost a month.
Best regards,
AronHello everyone,
Are there any news on this issue?
Have a nice day and a very good start of the week,
AronThis reply has been marked as private.Hi Naveen,
Thank you for the snippet, which works, and for adding a better validation to the field in the future.
Kind regards,
AronHi Naveen,
Thank you for the suggestion.
This solves the issue, but only partially, because it applies only to the year and not to the day/month: I am now no longer able to go back more than 100 years or forward to the next year, but I can still select a birth date in the future, between today and the 31.12.2019.Also the problem concerning validation of the date persists: I can still enter any number (or simply a series of dots) into the field, without triggering any error message.
Thank you in advance for looking more in-depth into the issue.
Kind regards,
AronThis reply has been marked as private.This reply has been marked as private.Hi Kiran,
Thank you, now it is much faster and way more reactive.
For future reference, may I ask what was causing the Ajax requests to take such a long time?
Have a nice evening,
AronThis reply has been marked as private.Hi Kiran,
Perfect, thank you, that worked like a charm!
Kind regards,
AronThis reply has been marked as private.Thank you Alex, I will keep an eye open for a developer feedback on this topic.
Have a nice weekend,
AronHi Alex,
Thank you for the reference to the snippet, but unfortunately this does not work for the “Expire date” field (nor does it add an option to the dropdown shown in my previous screenshot, located in the settings for the “Expire date” field in the backend, under Events > Settings > Custom fields > Expire date).
I used
$formats[] = 'd.m.Y';removing the comment and adding the missing semicolon but nothing has changed.
Do you have any other suggestion?Thank you also for having taken up my suggestion about automatic expiration date based on the event end date.
Kind regards,
AronSorry, one more question concerning the date format: is it possible to add the standard format configured in WordPress settings to the “Date Format” dropdown, or at least a “Custom” option?
Right now I see seven different options (see screenshot), but unfortunately none corresponds to my needs (nor to the settings used in the rest of the website).Thank you
Hi Alex,
Thank you for figuring it out. 😉
I re-enabled it also on the other CPTs.I have one more question concerning the Expire date of events: is it possible to automatically configure the end date of an event as its expire date? I understand that many users will prefer to keep their past events, but this leaves also some issues open, the main one being that some users will prefer to update a past event instead of paying to publish a new one (by expiring past events, this could be avoided).
Thank you and kind regards,
Aron
