[wp-trac] [WordPress Trac] #58814: Intensionally inset general->timezone_string field wrong format makes error in 'Time Format' & 'Date Format'

WordPress Trac noreply at wordpress.org
Mon Jul 17 01:13:31 UTC 2023


#58814: Intensionally inset general->timezone_string field wrong format makes error
in 'Time Format' & 'Date Format'
-----------------------------------------------+---------------------------
 Reporter:  mrinal013                          |       Owner:  (none)
     Type:  defect (bug)                       |      Status:  new
 Priority:  normal                             |   Milestone:  Awaiting
                                               |  Review
Component:  Administration                     |     Version:
 Severity:  normal                             |  Resolution:
 Keywords:  has-screenshots close 2nd-opinion  |     Focuses:
-----------------------------------------------+---------------------------
Changes (by costdev):

 * keywords:  needs-privacy-review has-screenshots => has-screenshots close
     2nd-opinion
 * version:  trunk =>
 * severity:  major => normal


Comment:

 Hi @mrinal013, thanks for opening this ticket!

 I'm not seeing how these values could be invalid without intentionally
 modifying them to be. [https://github.com/wordpress/wordpress-
 develop/blob/150cced9af2f39be1675a532dc99f362e788aeb7/src/wp-
 includes/functions.php#L6522 The values] are hardcoded with a prefix of
 [https://github.com/wordpress/wordpress-
 develop/blob/150cced9af2f39be1675a532dc99f362e788aeb7/src/wp-
 includes/functions.php#L6589 "UTC"] and [https://github.com/wordpress
 /wordpress-develop/blob/150cced9af2f39be1675a532dc99f362e788aeb7/src/wp-
 includes/functions.php#L6580-L6584 + or -]. Anyone using DevTools or
 JavaScript to modify these values should look at how the existing values
 are formatted before setting their own.

 If WordPress Core provided a filter for these timezone choices and lacked
 adequate validation, this would be a Core bug. However, this appears to be
 a warning created through intent, rather than a bug.

 -----

 - Removing `needs-privacy-review` as this doesn't relate to privacy.
 - Adding `close` and `2nd-opinion` to gather additional thoughts.
 - Setting `Severity` to `normal`.
 - Removing `Version` as the initial report states that this can be
 reproduced in earlier versions.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58814#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list