Post time incorrect by UTC offset in WP 6.1.1 on Atomic

[Nic-Sevic]

Quick summary

On WoA sites on WP 6.1.1 (latest) post times are offset by the equivalent of the difference between the sites timezone and UTC. When the site is set to UTC the time is correct.

Occasionally a new post will also display Schedule instead of Publish, I think because it’s done some conversion already and things the post is in the future even though it reports Immediately next to the time.

• It only happens with the block editor; time is correct when posted using classic editor
• I can’t reproduce on Simple or self hosted (with or without Jetpack)
• It doesn't happen when WP version is set to Previous (6.0.3)
• I confirmed with the Atomic team that this is not likely due to Atomic server settings already

Steps to reproduce

1. On a WoA site on latest version of WP, set the site time to some zone other than UTC (if you set to your TZ the testing is easier)
2. create a post and publish it immediately
3. click the publish time link and compare to the time in the popup

What you expected to happen

When posts are published immediately they should display the current time. Not the current time plus the UTC offset

What actually happened

On WoA sites on WP 6.1.1 (latest) post times are offset by the equivalent of the difference between the sites timezone and UTC. When the site is set to UTC the time is correct.

Context

p9F6qB-b40-p2#comment-51010

Platform (Simple, Atomic, or both?)

Atomic

Theme-specific issue?

no

Browser, operating system and other notes

No response

Reproducibility

Consistent

Severity

All

Available workarounds?

None

Workaround details

If you set the site time to UTC it will reflect correctly (according to UTC time)

[zdenys]

5821455-zd-woothemes Site's timezone is set to New York (aka EST). In order for the time next to Publish to be December 31, 2022 10:00 pm EST in the date picker they have to select 3AM January 1st 2023.

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• 5821455-zen
• 5827219-zen
• 5808896-zen
• 5833516-zen
• 5811299-zen
• 5837913-zen
• 5835486-zen
• 5855449-zen
• 5833365-zen
• 5808500-zen
• 5907979-zen
• 5917720-zen
• 5900931-zen
• 5979802-zen
• 5999819-zen
• 6014104-zen
• 6044854-zen
• 6089805-zen
• 6168910-zen
• 6250700-zen

[adelineyaw]

User report: 38948245-hc - in this instance, scheduled blog post for 16:10 ended up being published earlier at 11:10am.

User's workaround is to schedule posts via their mobile.

[zachspears]

I could not reproduce this issue, but given the multiple reports, I am moving this forward. Leaving Normal priority due to potential impact given the nature of the issue.

[donalirl]

It seems to be occurring on this simple site case too p2EDhh-1Ng-p2

[NoHopeRadio]

Another case here: 5827219-zen

Something I wanted to mention: on all the sites I've seen where this is happening, there seem to be hundreds of console errors when in the editor, all looking like this:

Moment Timezone has no data for WP. See http://momentjs.com/timezone/docs/#/data-loading/.

It seems to have resolved on my simple test site where I was examining the issue since yesterday. On my Atomic test site, it seems like the gap in time between the post time and the time it should be is always an extra GMT offset. So it's five hours earlier when set to UTC-5 or America/New_York, but it's 8 hours earlier than the set time if I set the time zone to Los Angeles. I believe that some declaration is getting processed twice, but I can't find what that would be. I can't seem to force a change by removing options either in the Network Admin or CLI.

[pauljacobson]

I believe we have another report along these lines in 5808896-zen

This site is on a WordPress.com Personal Plan.

[the-misha]

Another user report, Business plan site, 38466797-hc.