Opened 7 years ago

Closed 7 years ago

#10603 closed (wontfix)


Reported by: pcicman Owned by: nobody
Component: Forms Version: master
Severity: Keywords: forms date time datetime format templates
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Wouldn't it be better to move DEFAULT_DATE_INPUT_FORMATS to

DEFAULT_DATE_INPUT_FORMATS doesn't match for most European Countries, so only one way how to change it is putting format for every form field through input_formats argument, what's just not so nice.

Second problem is output (display) format of Date field. I think its similar to #3672. It just doesn't care of INPUT_FORMAT because its not implemented.

There are actually some formats available in, eg:


which doesn't really make much sense.


Can't be this settings just combined together to one default date/time/datetime formats, which will be used for all date/time input/display?

In this case eg DATE_FORMAT can stay in, but should may be changed to tuple, which will contain one or more formats. For input, all formats will be available, for output will be by default taken the very first format.

I think this will make sense also for international pages, where will be still possible to provide different settings for different country/language/...

unicode for date/time then can also return right output string (formated). This may be very useful for rendering date/time in template.

Change History (1)

comment:1 Changed 7 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

This isn't the correct solution for this problem, since date input formats is a localisation issue, not something the installer of an application should configure in settings. Your approach also fails in the very common case when a site is available in more than one locale at a time.

The correct solution here is that those formats either have to be localised or (preferably) made available as metadata for each locale. That's something we're working on already -- providing sensible values for those things, as well as locale-aware validation for other form fields that change values.

Note: See TracTickets for help on using tickets.
Back to Top