Dear GD support team,
I have a date of birth field set up for one of my listing packages, but unfortunately it is not working as expected. The “Date Range” field in the custom field settings contains the value “c-100:c+0” so I would expect to be able to select a birthdate between “100 years ago” (therefore the 11.09.1919) and today (as it is quite normal and standard for a date of birth field, no date in the future should be selected), but instead I can also do some fancy, unexpected stuff:
- I can select a date in the future, and by clicking repeatedly on the button for going to the next month I can even potentially select a birth date many years in the future. It seems that the “c+0” part of the date range is simply ignored.
- On the other hand, I can also go back to the past, for example to the year 1919 (100 years ago, as expected, cool… or maybe not?), but then I can also go even further back, 100 years at a time (1819, 1719, 1619, 1519, etc.), but unfortunately I can no longer come back to the future (some time travel rules apply here as it seems…). The date range is dynamic, so if I go back to 1919, the date range will be applied to the selected date instead of today’s date, which breaks the whole idea of the initial date range.
It is ok if the dates outside the selected range cannot be physically hidden from the calendar, but they should be at least disabled, making them no longer selectable.
In addition, a correct validation should be applied to the field if an entry is made manually (validating both the date range and the valid date format), because right now we can not only enter a date outside the desired range, but also some complete nonsense (e.g. “99.99.9999” or “………………..”), without triggering an error message on form submission.
Thank you in advance for your feebback.
Kind regards,
Aron