Make WordPress Core

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#48239 closed enhancement (maybelater)

Use a date in General Settings greater than the 12th day for clarity at a glance

Reported by: garrett-eclipse's profile garrett-eclipse Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Date/Time Keywords:
Focuses: ui, administration Cc:



Currently the General Settings for Date Format uses the current date to populate the available format options. This works as expected but I find at a glance if the current day is less than the 12th day of the month it's hard to distinguish the m/d/Y vs d/m/Y format. If a more standard date that's greater than 12 is used it makes it easier to distinguish the two formats at a glance as it's easy to tell which number is the day vs the month as months only go up to 12.

I hope I've explained that, screenshot coming.


Attachments (1)

Screen Shot 2019-10-07 at 10.19.55 AM.png (17.5 KB) - added by garrett-eclipse 5 years ago.
At a glance date format had to tell.

Download all attachments as: .zip

Change History (7)

5 years ago

At a glance date format had to tell.

#1 @knutsp
5 years ago

Below the radio buttons there is a Preview. I suggest a second preview date and time following the current, for both date and time. Time should be PM.

#2 @Rarst
5 years ago

I get your point in principle for arbitrary date (which is why I by far prefer ISO formats in practice, e.g. 2019-10-07).

However in this specific instance the date is not ambiguous, it uses the current day and is immediately followed by human-readable format value.

I am not sure what practical improvement is possible here.

We could do something like Go with standardized value for date examples, but frankly I find that harder to explain than PHP formats.

#3 @johnbillion
5 years ago

Devil's advocate: If the date is ambiguous on the General Settings screen, it'll be ambiguous for your users.

#4 @Rarst
5 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from new to closed

After thinking on this for a while, I feel the improvement is insufficient to change existing behavior here.

This would be a stronger argument for initial design, but for something that has been in place for a very long time, and is sufficiently clear with explicit date formats, it's not worth messing with.

There has been proposal for rethinking and extending use of date formats in general, but it doesn't have traction at the moment. If it picks up steam we can revisit how we present the options as part of larger change.

#5 @garrett-eclipse
5 years ago

Sounds good, thanks @Rarst

#6 @sabernhardt
4 years ago

#51499 was marked as a duplicate.

Note: See TracTickets for help on using tickets.