You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When any Date Separator option except 'None' is used and the date is manually typed in without using the datepicker or any separators, the resulting date in changed to a different date when automatically formatted to include the separators.
Steps to reproduce
In a Date & Time field (using Type of Date, haven't tested with Both), type in a valid date but without any separators
When focus is lost and the date is auto-formatted to include separators, the date is changed to a different date
Examples of before and after with two different dates (01012024 changed to 1/12/2024 and 12312023 changed to 12/12/2023):
Expected behavior
Date should be formatted to include the separators without changing the date entered by the user
Craft & Plugin Info (please complete the following information):
Craft Version: Pro 4.6.1
Freeform Version: 4.1.13
Freeform Edition: Pro
Fresh Install or Upgrade: Fresh install
The text was updated successfully, but these errors were encountered:
Disabling the datepicker prevents the date from being changed incorrectly, but obviously doesn't format the date automatically so requires the user to make sure this is done manually. Using as a workaround for now.
Describe the bug or issue you're experiencing
When any Date Separator option except 'None' is used and the date is manually typed in without using the datepicker or any separators, the resulting date in changed to a different date when automatically formatted to include the separators.
Steps to reproduce
Examples of before and after with two different dates (01012024 changed to 1/12/2024 and 12312023 changed to 12/12/2023):
Expected behavior
Date should be formatted to include the separators without changing the date entered by the user
Craft & Plugin Info (please complete the following information):
The text was updated successfully, but these errors were encountered: