Skip to content

Conversation

@westonruter
Copy link
Member

@westonruter westonruter commented Jan 13, 2026

Trac ticket: https://core.trac.wordpress.org/ticket/64496


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Drafted Commit Message

Administration: Avoid PHP type error with gmdate() in wp_dashboard_recent_posts().

This fixes an issue when a non-integer is returned by get_the_time( 'U' ) which can occur when a plugin filters get_the_time. The non-relative date is displayed in the Activity dashboard widget in this case.

Developed in #10729

Props sabernhardt, vanhoucke, westonruter.
Fixes #64496.

@github-actions
Copy link

github-actions bot commented Jan 13, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props sabernhardt, westonruter.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Comment on lines 1017 to 1019
if ( ! is_int( $time ) || gmdate( 'Y', $time ) !== $year ) {
/* translators: Date and time format for recent posts on the dashboard, from a different calendar year, see https://www.php.net/manual/datetime.format.php */
$relative = date_i18n( __( 'M jS Y' ), $time );

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This approach silences the error and shows date information, but the date is not reliable with non-integers.

  • The numeric string with Simple Location displayed as the next day for two of my posts.
  • date_i18n() will give the current date whenever its $timestamp_with_offset parameter is not numeric.
screenshots of Activity widget with PR 10729

I still think that blank space is better than displaying inaccurate information, but this achieves the main focus of the ticket by preventing a predictable fatal error. PHP 8.4.0 does not complain (yet) about using a false value from get_the_time() in the '%1$s, %2$s' string on line 1036.


I needed to include results for at least one of the date translation plugins, and WP-Parsidate filters get_the_time well. It returns an integer when the format is 'U', so it does not cause an error in the widget before or after applying either patch. It also returns the Persian time and date strings for displaying in the widget.

(Both the 'Change Locale in admin' and 'Shamsi date' checkboxes should be checked.)
WP-Parsidate Settings

Copy link
Member Author

@westonruter westonruter Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't feel strongly. If you want my suggestion reverted then that is fine with me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reverted my changes. I also missed that I was possibly passing non-int into date_i18n().

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Argh. I was just too slow to write this response before you reverted.

I tested again without the patch. The numeric string already gave dates one day off (without including the current year), and the false value gave the current date and no time.

According to that testing, this would not introduce inaccurate dates in the widget. That suggests your way is the more appropriate change, even though it is not my preference.

Relatively few sites filter get_the_time( 'U' ) in the admin to a non-integer anyway, and both directions should be viable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused because in my way I was possibly passing a non-integer value into date_i18n().

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about this?

--- a/src/wp-admin/includes/dashboard.php
+++ b/src/wp-admin/includes/dashboard.php
@@ -1014,7 +1014,9 @@ function wp_dashboard_recent_posts( $args ) {
 
 			$time = get_the_time( 'U' );
 
-			if ( gmdate( 'Y-m-d', $time ) === $today ) {
+			if ( ! is_int( $time ) ) {
+				$relative = null;
+			} elseif ( gmdate( 'Y-m-d', $time ) === $today ) {
 				$relative = __( 'Today' );
 			} elseif ( gmdate( 'Y-m-d', $time ) === $tomorrow ) {
 				$relative = __( 'Tomorrow' );
@@ -1033,7 +1035,7 @@ function wp_dashboard_recent_posts( $args ) {
 			printf(
 				'<li><span>%1$s</span> <a href="%2$s" aria-label="%3$s">%4$s</a></li>',
 				/* translators: 1: Relative date, 2: Time. */
-				sprintf( _x( '%1$s, %2$s', 'dashboard' ), $relative, get_the_time() ),
+				sprintf( _x( '%1$s, %2$s', 'dashboard' ), $relative ?? get_the_date(), get_the_time() ),
 				$recent_post_link,
 				/* translators: %s: Post title. */
 				esc_attr( sprintf( __( 'Edit &#8220;%s&#8221;' ), $draft_or_post_title ) ),

If $relative is not available due to get_the_time( 'U' ) returning non-integer, then we can fall back to get_the_date().

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passing it to date_i18n() is not ideal, but the function has a fallback:

// If timestamp is omitted it should be current time (summed with offset, unless `$gmt` is true).
if ( ! is_numeric( $timestamp ) ) {
// phpcs:ignore WordPress.DateTime.CurrentTimeTimestamp.Requested
$timestamp = current_time( 'timestamp', $gmt );
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But that fallback results in the current date being returned, and not the publish date of the post, right?

Copy link
Member Author

@westonruter westonruter Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With 096cea0, given this filer code:

add_filter(
	'get_the_time',
	function ( $the_time ) {
		return (string) $the_time;
	}
);
Without filter With filter
image image


if ( gmdate( 'Y-m-d', $time ) === $today ) {
if ( ! is_int( $time ) ) {
$relative = null;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This direction seems better.

Also, if you move get_the_date() to this line, the null coalescing operator should be unnecessary.

Suggested change
$relative = null;
$relative = get_the_date();

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point. Added in 958ce5c. Then I renamed the variable since it's no longer specifically relative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants