Make WordPress Core

Opened 2 years ago

Last modified 2 years ago

#55685 new enhancement

Date setting should have two more options: j.n.Y and d.m.Y

Reported by: daedalon's profile Daedalon Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.9.3
Component: Date/Time Keywords:
Focuses: ui, administration Cc:


Everytime I set up a WordPress site, I have to consult the PHP date formatting rules to get the site to show dates in the way that is standard in much of Europe, Post-Soviet countries, and many other places: j.n.Y. That is, 31.12.2022 for the last day of this year, or 5.5.2022 for today, with no leading zeroes.

This is a shortened way of the official d.m.Y, which shows 05.05.2022 for today, with leading zeroes. Most of the time I see all types of organizations and individuals prefer the shorter version without leading zeroes, but this official notation has plenty of users as well.

Both would be so helpful for so many users to have as one-click options in the site's General Settings page that I think it'd be great to add them there.

More info

Searching the latter page for "d.m" finds 36 countries where either of these formats is in widespread usage. The combined population of these countries is approx. a billion people (e.g. Russia, Germany, Ukraine, Turkey, Israel, Poland). In addition to these, the list shows approx. 100 countries following the DMY order of date representation, without specifying the separators (dots "." or otherwise). The combined population in countries using j.n.Y or d.m.Y representations of dates might be well in excess of 1 billion people.

Change History (2)

#1 @fierevere
2 years ago

Localized WordPress (when you select language at installation) will use locale time representation.

So d.m.Y for russian for example

#2 @SergeyBiryukov
2 years ago

  • Component changed from General to Date/Time

Hi there, thanks for the ticket!

As noted above, one of the date format options is translatable, so localized WordPress packages can (and already do) add their own preferred date format by translating the __( 'F j, Y' ) string, for example, to d.m.Y.

That said, given its widespread usage, I think d.m.Y would beneft from being added as separate option, so that one could choose it regardless of the current user's locale or the admin locale. It would then be displayed and recognized as one of the officially supported options, instead of "Custom".

I'm less sure about j.n.Y. In the latest quarter of the year, a date like 10.11.2022 would be the same in both formats, so it might be hard to tell the difference from d.m.Y. The was also a concern voiced previously in comment:5:ticket:28447 about adding too many options. Other than that, I don't have any strong objections.

Slightly related: #48239

Note: See TracTickets for help on using tickets.