[wp-trac] [WordPress Trac] #60629: PHP Fatal error: Uncaught TypeError: gmdate(): Argument #2 ($timestamp) must be of type ?int, string given in wp-admin/includes/dashboard.php:1025

[WordPress Trac]

#60629: PHP Fatal error:  Uncaught TypeError: gmdate(): Argument #2 ($timestamp)
must be of type ?int, string given in wp-admin/includes/dashboard.php:1025
--------------------------+--------------------------------
 Reporter:  vanhoucke     |       Owner:  hellofromTonya
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  6.7
Component:  Date/Time     |     Version:  6.4.3
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  php-compatibility
--------------------------+--------------------------------
Changes (by hellofromTonya):

 * owner:  (none) => hellofromTonya
 * status:  new => assigned
 * milestone:  Awaiting Review => 6.7


Comment:

 Related: #56358, #57035, #58986.

 Each of these tickets is dealing with the same issue, which I summarized
 in [57035#comment:39]:

 >I'm thinking this area needs a deeper contextual dive as well as
 consideration and testing to raise confidence of no side effects or
 regressions being introduced. It'll also need more test coverage (happy
 and unhappy paths).
 >
 >The challenges:
 >* robust solution to handle all timezones include partial hour timezones.
 >>The `gmt_offset` can be a float/double for partial-hour timezones such
 as +5:30 UTC for India and Sri Lanka.
 >* review of what values `gmt_offset` should and could have.
 >* and cross-version compatibility for the PHP versions WP supports.
 >
 >I'm also curious of how this is solved in other projects.
 >
 Pulling it into 6.7 and self-assigning with intent to help shepherd the
 effort for these tickets.

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