Date Time and UTC / GTM Timezone is not synchronizing

[lamarajan]

Hello Core Team,

I have found one serious bug in WordPress Related to post publish Date Time. The issue is Time of published post is not synchronizing UTC timezone.

Scenario, I am in Nepal and My WordPress site is set in +0 GMT. Now, I change the timezone of Site to Kathmandu, Nepal (Local Timezone). And, I create a post and publish at 8:00pm (local time +5:45 GMT). Now I get back to setting and changed the timezone ( +0 GMT ). Now I get back to my previos post. And I get my post published time is 8:00PM +0 UTC. This is not a correct time of my post is published.

I have attached the video link and also attached the quick demo video.
​https://www.awesomescreenshot.com/video/27695979?key=eacbfc62438d79ed5dc00b8f095b0009

If you have question please let me know,

Thanks,
Rajan Lama (@lamarajan)

[lamarajan]

This the screen recorded video for the issue.

[narenin]

Hi,

I am also able to replicate the same at my end.

[narenin]

Also that Timezone value(UTC+5:45) show as per the current setting it does not show according to the timezone we had during the post publish time.

Screenshot : ​https://ibb.co/xmNdqvh

[Rarst]

WordPress de facto does not support changing time zone, all post times are considered to be in current settings time zone, as you have observed.

Supporting this would require either significant effort to migrate local times every time time zone is changed (there is no strong precedent and support in core for such mechanics) or moving to using UTC times as canonical. We have considered the latter, but it conflicts with support for scheduling posts in core, which requires working with local times (since the future state of time zone relative to UTC is not knowable).

In a nutshell, this would be a complicated thing to implement and demand for it has been relatively low (on a WordPress scale).

[lamarajan]

Hello @Rarst ,

Thank you for your suggestion and I understand demand for it has been relatively low but I think this is one of the bug that needs to be handled someday.

Thanks,
@lamarajan