Defect #668
Date input fields don't respect date format settings
| Status: | New | Start date: | 2008-02-15 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | UI | |||
| Target version: | Candidate for next major release | |||
| Resolution: | Affected version: |
Description
The input box next to calendar, shows always "YYYY-MM-DD" and doesn't follow the language settings.
This is very confusing at least in finnish language, because we never type it like that.
.b
app_helpers_application_helper_rb.diff 
- Path to fix helper function calendar_for
(707 Bytes)
Related issues
History
#1
Updated by Antti Perkiömäki over 11 years ago
I tried a little change in caldendar-fi.js file:
Calendar._TT["DEF_DATE_FORMAT"] = "%Y-%m-%d"
==>
Calendar._TT["DEF_DATE_FORMAT"] = "%d.%m.%Y"
Did not change the behaviour though :) The date format was still YYYY-MM-DD
Not really a programmer so no clue why the change didn't work. Anyways tried with several browsers so might need change to some other place to change the date format.
#2
Updated by Bastian Salmela over 11 years ago
aah.. i tried those too, and some other tricks... but best I got was calendar-widget changing the field correctly (respecting dd-mm-yyyy) when I clicked a date.. but still, everytime I am adding new issue, or editing old one, the date in field gets defaulted in wrong order.
I dont know ruby, so after hour of going through sources I just gave up :)
.b
#3
Updated by Jean-Philippe Lang over 9 years ago
- Category set to UI
#4
Updated by Filip Morávek about 9 years ago
- Assignee set to Jean-Philippe Lang
this date format is confusing for normal users
#5
Updated by Felipe Cardoso Martins about 9 years ago
- File app_helpers_application_helper_rb.diff added
#6
Updated by Stuart Cianos almost 9 years ago
#7
Updated by Jean-Philippe Lang over 6 years ago
- Subject changed from date input fields don't respect date format settings to Date input fields don't respect date format settings
- Target version set to Candidate for next major release
#8
Updated by Toshi MARUYAMA almost 6 years ago
- Duplicated by Defect #14857: Date localization don't take effects over Date Select fields added
#9
Updated by Ivan Cenov over 5 years ago
The defect is in Redmine 2.4.2 too.
#10
Updated by Luis Serrano Aranda over 5 years ago
+1
#11
Updated by Ján Regeš over 4 years ago
+1
#12
Updated by Laurent Dairaine about 4 years ago
+1
#13
Updated by Bruno Ilponse about 4 years ago
+1
#14
Updated by Leandro Gehlen about 4 years ago
I created a jquery plugin to solve this problem:
jQuery Binding Format
#15
Updated by Alessandro Zucchi over 3 years ago
+1
#16
Updated by Alessandro Lanza over 3 years ago
+1
#17
Updated by Vincent Robert over 3 years ago
Leandro, can you please explain how to use your jquery plugin with standard Redmine date fields?
Have you ever integrate it to Redmine?
Thanks
#18
Updated by Luiz Moura about 3 years ago
+1
#19
Updated by Alexander Scherdo over 2 years ago
+1
#20
Updated by Bavo Cuypers over 1 year ago
+1
#21
Updated by Jonas De Meulenaere 11 months ago
+1.
We're currently upgrading from Redmine 2.4.3 to 3.4.6.stable, and it strikes me that this input date formatting problem is around for so long. So for us, it got worse:
- Our output date formatting is dd/MM/yyyy
- In 2.4.3 you get a calendar icon next to the input field. When selecting a date, it copies it in the input field in the format yyyy-MM-dd
- In 3.4.6 there is no calendar icon. The calendar shows up directly when clicking the input field. When selecting a date, it copies it in the input field in the format MM/dd/yyyy.
"yyyy-MM-dd" is still clear to us, at least it doesn't switch the month and the day.
What is more: when entering a date manually (the mask is MM/dd/yyyy), it applies a "ceiling" function to each date part. So when mistakenly typing e.g. 18, 05, 2018, meaning May 18, 2018, the 18 is converted automatically to 12, and without any warning it is set to 12/05/2018 (December 5th).