WordPress.org
Get WordPress

Make WordPress Core

Opened 15 months ago

Closed 5 weeks ago

Last modified 5 weeks ago

#62616 closed defect (bug) (duplicate)

Time Setting in WP general settings is not followed in Update screen

Reported by: neo2k23's profile neo2k23 Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.9
Component: Date/Time Keywords: has-patch close 2nd-opinion
Focuses: ui, administration Cc:

Description

The Time setting as set in the wordpress general settings is not followed in the wordpress update screen. See explaining image attached or the link

​https://share.zight.com/nOu4dqbk

Thank you

Attachments (1)

time-setting.jpg​ (234.4 KB) - added by neo2k23 15 months ago.
screenshot of both screens

Download all attachments as: .zip

Change History (7)

@neo2k23
15 months ago

screenshot of both screens

#1 @ankitkumarshah
15 months ago

Reproduction Report

Description

This report validates whether the issue can be reproduced.

Environment

  • WordPress: 6.8-alpha-59274-src
  • PHP: 8.2.25
  • Server: nginx/1.27.2
  • Database: mysqli (Server: 8.0.40 / Client: mysqlnd 8.2.25)
  • Browser: Chrome 131.0.0.0
  • OS: macOS
  • Theme: Twenty Twenty-Five 1.0
  • MU Plugins:
    • Test Plugin
  • Plugins: Test Reports 1.2.0

Actual Results

  1. ✅ Error condition occurs (reproduced).

Supplemental Artifacts

​https://utfs.io/f/TnWMEUzoUd85REIHYCZSIPw9GZ1j3xLCbU6mE4de0VBfrH7T

This ticket was mentioned in ​PR #7921 on ​WordPress/wordpress-develop by ​@abcd95.
15 months ago #2

  • Keywords has-patch added

Trac ticket: 62616

#3 @sainathpoojary
15 months ago

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/7921

Environment

  • WordPress: 6.8-alpha-59274-src
  • PHP: 8.2.26
  • Server: nginx/1.27.3
  • Database: mysqli (Server: 8.0.40 / Client: mysqlnd 8.2.26)
  • Browser: Chrome 131.0.0.0
  • OS: macOS
  • Theme: Twenty Twenty-Five 1.0
  • MU Plugins: None activated
  • Plugins: None activated

Actual Results

  1. ✅ Issue resolved with patch.

Supplemental Artifacts

Before:

https://utfs.io/f/PL8E4NiPUWyOpRDMCyaQVMXblTwtAz0NaoWOrjEIdxin63gS

After:

https://utfs.io/f/PL8E4NiPUWyONjltsKpMS0asiF6Z4m28LU1tPANvKXdxqzRw

#4 follow-up: @swissspidy
15 months ago

  • Keywords close 2nd-opinion added

I think we have a few duplicates about this already, but basically the time format is mainly meant to apply on the frontend, not everywhere. So this is not a bug.

#5 in reply to: ↑ 4 ; follow-up: @neo2k23
15 months ago

Replying to swissspidy:

I think we have a few duplicates about this already, but basically the time format is mainly meant to apply on the frontend, not everywhere. So this is not a bug.

I disagree as half of the world does not read am/pm format but 24 hours format. Please adapt and adjust the update.php

Thank you

#6 in reply to: ↑ 5 @SergeyBiryukov
5 weeks ago

  • Component changed from General to Date/Time
  • Focuses ui administration added
  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Hi there, thanks for the ticket!

Replying to swissspidy:

I think we have a few duplicates about this already, but basically the time format is mainly meant to apply on the frontend, not everywhere. So this is not a bug.

Correct, see [35811] and the discussion in #30864.

Replying to neo2k23:

I disagree as half of the world does not read am/pm format but 24 hours format. Please adapt and adjust the update.php

These format strings are translatable, so locale managers can adjust them for a specific locale as needed.

This appears to be a duplicate of #48063, let's continue the discussion there.

Last edited 5 weeks ago by SergeyBiryukov (previous) (diff)
Note: See TracTickets for help on using tickets.