On version 1.2.1 - commit 590b73e25e09bc6f8781585604b18738bc79fbdf
When setting the time for autoclose I enter a local time and press save.
When I reopen that same dialogue it is 12 hours later than expected. My timezone is UTC+12.
A timezone issue has been reported in the Autoclose topic feature, where the time entered by users in their local timezone is not accurately reflected. rhulse shared an example of this issue, where the time is displayed 12 hours later than expected in their UTC+12 timezone. codinghorror explained that the autosave feature currently uses server time, but should use local time instead.
Mittineague mentioned that time-related issues have been present for a while, and provided screenshots showing discrepancies in times displayed for a member’s activity and actual post. cpradio suggested that caching might be contributing to the issue, but also experienced strange behavior with the Autoclose feature.
However, neil has since fixed the bug, and the fix will be included in the 1.3 release. The updated feature will now take into account the user’s local timezone when entering the auto-close time.
On version 1.2.1 - commit 590b73e25e09bc6f8781585604b18738bc79fbdf
When setting the time for autoclose I enter a local time and press save.
When I reopen that same dialogue it is 12 hours later than expected. My timezone is UTC+12.
The auto save absolute time entry appears to use server time. It does not use local time, but it should. Cc: @neil
We’ve noticed that time has been a bit wonky for as long as I can remember.
Not a top priority since most don’t even notice, but @cpradio @TechnoBear and I are the exception, we’ve tested heavily.
For an example, screen captured just now, the times on a member’s “activity” and the actual post aren’t always in sync
from Activity
the post
True, but I think that’s more from caching than anything else, but I could very well be wrong with that. The Timezone issue in Autoclose may explain some of the weirdness I’ve seen around closing topics lately.
For 1, it closed immediately when I put in 2192 hours from last response, and 2, I’ve seen it not take my change, so I entered it again, and then it takes.
I fixed the bug mentioned in the op today, so it will make it into the 1.3 release. Entering the auto-close time now takes into account your local time zone.
https://github.com/discourse/discourse/commit/ea8cf1a208d198ae1d7ff1e795830766c01be7d0