[wp-trac] [WordPress Trac] #26977: Changing TimeZone Does Not Take Into Account Existing Post Timestamps

[WordPress Trac]

#26977: Changing TimeZone Does Not Take Into Account Existing Post Timestamps
--------------------------+------------------------------
 Reporter:  cais          |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Date/Time     |     Version:  3.8
 Severity:  normal        |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------

Comment (by cais):

 Replying to [comment:1 DrewAPicture]:
 > This seems like the expected behavior here. The post time – rather the
 post date – is based on the current time adjusted for the current GMT
 offset at the time of saving.

 I would say this is expected bahavior simply because that is exactly how
 it is working but I still would not say it is correct.

 > So to expect a saved value to adjust based on a new GMT offset seems out
 of scope. If I'm misunderstanding the premise, please correct me :-)

 This is exactly the premise I am suggesting ... being out of scope would
 imply it is not possible to make these changes.

 > Suggest invalid/wontfix.

 I could see a "wontfix" resolution on this because it is very much edge-
 cases involved but that still does not make the issue invalid ... just
 something that was chosen to be ignored.

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