Opened 7 weeks ago
Last modified 7 weeks ago
#62616 new defect (bug)
Time Setting in WP general settings is not followed in Update screen
Reported by: | neo2k23 | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | trunk |
Component: | General | Keywords: | has-patch close 2nd-opinion |
Focuses: | 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)
Change History (6)
#1
@
7 weeks 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
- ✅ Error condition occurs (reproduced).
Supplemental Artifacts
https://utfs.io/f/TnWMEUzoUd85REIHYCZSIPw9GZ1j3xLCbU6mE4de0VBfrH7T
This ticket was mentioned in PR #7921 on WordPress/wordpress-develop by @abcd95.
7 weeks ago
#2
- Keywords has-patch added
Trac ticket: 62616
#3
@
7 weeks 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
- ✅ Issue resolved with patch.
Supplemental Artifacts
Before:
After:
#4
follow-up:
↓ 5
@
7 weeks 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
@
7 weeks 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
screenshot of both screens