WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 21 months ago

#9759 closed enhancement (duplicate)

timezone_string UI: scanning a long list of cities is too hard

Reported by: andy Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Date/Time Keywords: needs-patch
Focuses: Cc:

Description

Anyone looking for their time zone in North or South America may have a very long list of cities to scan through. On my Debian host (Dreamhost) there are over 150 cities in the America list.

I live in Texas. None of Texas' major cities are listed. To select US Central, I guessed wrongly several times before I found Chicago.

This list is populated from timezone_identifiers_list() which can result in a very long list. We could improve this by listing US time zones at the top with appropriate strings as values, e.g. US Central -> America/Chicago. This simple logic would save a lot of frustration.

Change History (7)

comment:1 filosofo5 years ago

See discussion here: #3962

comment:2 Denis-de-Bernardy5 years ago

  • Milestone changed from Unassigned to 2.8

comment:3 MattyRob5 years ago

  • Severity changed from major to normal

Okay I agree the list is pretty long but you are only ever going to have to make the selection once per blog unless you move home often. Also, you state that you guessed wrongly other cities that should be in your time zone - sorry but you can't blame software for you firstly guessing, secondly guessing badly and thirdly having no idea of other cities in the same time zone as you.

comment:4 Denis-de-Bernardy5 years ago

  • Keywords needs-patch added
  • Milestone changed from 2.8 to Future Release

comment:5 Denis-de-Bernardy5 years ago

  • Priority changed from high to normal
  • Type changed from defect (bug) to enhancement

comment:6 TECannon4 years ago

See also: #10324

comment:7 helenyhou21 months ago

  • Component changed from UI to Date/Time
  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Closing in favor of #10660, which has a patch that does an API call to suggest a timezone based on your location, bypassing the need to look at that long list and/or make it US-centric instead.

Note: See TracTickets for help on using tickets.