You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is incorrect. For comparison, refer to core's get_post_time() function as used by get_the_date() as used in classic themes. It useswp_date() as follows:
When the $timezone parameter is not passed to wp_date() then it uses the current timezone as specified in the blog's settings.
Testing
I added a Date block in a row in the Single template in Twenty Twenty-Five:
I also have my timezone set to America/Los Angeles:
The current time for me right now is 22:35 (10:35pm) on August 31st. In the block editor, I see this reflected correctly when showing the template in the block editor:
However, if I view the post on the frontend, I see September 1st, since that is the current date in UTC/GMT:
When I switch to the code in this branch so that wp_date() is used instead, then I see the expected date of August 31st:
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.
If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
Flaky tests detected in 580f81f.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #39984.
The date/time being displayed in the Date block is currently using
gmdate()
:gutenberg/packages/block-library/src/post-date/index.php
Line 79 in a040815
This is incorrect. For comparison, refer to core's
get_post_time()
function as used byget_the_date()
as used in classic themes. It useswp_date()
as follows:When the
$timezone
parameter is not passed towp_date()
then it uses the current timezone as specified in the blog's settings.Testing
I added a Date block in a row in the Single template in Twenty Twenty-Five:
I also have my timezone set to America/Los Angeles:
The current time for me right now is 22:35 (10:35pm) on August 31st. In the block editor, I see this reflected correctly when showing the template in the block editor:
However, if I view the post on the frontend, I see September 1st, since that is the current date in UTC/GMT:
When I switch to the code in this branch so that
wp_date()
is used instead, then I see the expected date of August 31st: