#28522 closed Bug (needsinfo)
Django seems to ignore global DATE_INPUT_FORMATS and TIME_INPUT_FORMATS when set in settings
| Reported by: | Dan Swain | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.11 |
| Severity: | Normal | Keywords: | settings DATE_INPUT_FORMATS TIME_INPUT_FORMATS forms validation |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Django seems to be completely ignoring the global settings variables DATE_INPUT_FORMATS and TIME_INPUT_FORMATS. I have a question posted here that explains the problem.
https://stackoverflow.com/questions/45827973/cannot-successfully-parse-django-datefield-in-form
Dan Swain
Change History (2)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Reading #13339 might help understand the issue. I don't have much experience with localizations in forms myself. Please reopen the ticket if you can provide some code to reproduces a problem that contradicts the documentation.
Note:
See TracTickets
for help on using tickets.
Can you please provide a test for Django's test suite (or at least some minimal code) that demonstrates the issue? Linking to another website to explain the issue isn't ideal because if that disappears then we have no explanation of the issue. Thanks.
p.s. Before creating a ticket, you might try our support channels to confirm there's a bug and not a usage mistake.