Chris027 Posted November 25, 2019 Posted November 25, 2019 Hi guys - I updated to 4.4.9 this morning before publishing an article. Now the time on the article I just published is UTC I believe. If I change publishing time to 10am central US time, it will say the article was published 6 hours ago.
Maxxius Posted November 26, 2019 Posted November 26, 2019 @Chris027 does this still bother you? is that a real bug? I'm holding off the upgrade now.
Stuart Silvester Posted November 26, 2019 Posted November 26, 2019 4.4.9 Did not contain any changes for Pages or related to time/dates. - I would recommend submitting a ticket if you are experiencing issues.
Chris027 Posted November 26, 2019 Author Posted November 26, 2019 6 hours ago, Maxxius said: @Chris027 does this still bother you? is that a real bug? I'm holding off the upgrade now. Yeah, I'm not sure what's going on. 3 hours ago, Stuart Silvester said: 4.4.9 Did not contain any changes for Pages or related to time/dates. - I would recommend submitting a ticket if you are experiencing issues. I looked through the release notes before upgrading and after and can't figure out what could be the issue.
opentype Posted November 26, 2019 Posted November 26, 2019 There are lots of date fields for Pages databases. record_saved, record_updated, record_publish_date, record_last_comment, record_edit_time … It’s easy to get confused, but it is probably working as intended.
Chris027 Posted November 26, 2019 Author Posted November 26, 2019 10 minutes ago, opentype said: There are lots of date fields for Pages databases. record_saved, record_updated, record_publish_date, record_last_comment, record_edit_time … It’s easy to get confused, but it is probably working as intended. It can't be because something has changed and it doesn't make sense. Check the first article in the upper left. Published around 10am central time Monday. It says 22 hours ago and that's correct. I went into the article and changed nothing, looked at the published time that said 10:15 AM, but didn't change it or even put my cursor in the field. 10:15 is correct. I hit save. Now the article says it was published at 4:15 am. That's UTC. My server time is correct although in the eastern US time zone.
opentype Posted November 26, 2019 Posted November 26, 2019 If you can replicate an unwanted time change, open a ticket.
Martin A. Posted November 26, 2019 Posted November 26, 2019 8 hours ago, Stuart Silvester said: 4.4.9 Did not contain any changes for Pages or related to time/dates. - There is nothing in the changelog about it, but there is a change in \IPS\Helpers\Form\Date.
Stuart Silvester Posted November 26, 2019 Posted November 26, 2019 2 hours ago, Martin A. said: There is nothing in the changelog about it, but there is a change in \IPS\Helpers\Form\Date. You're right. The change log is missing a few items. We'll get that updated. We're currently looking into the date issue.
Gabriel Torres Posted November 27, 2019 Posted November 27, 2019 @Stuart Silvester @Chris027 @Martin A. Just to let you guys know that we are facing the same issue here. Times are now in UTC, and as our server is configured as UTC +3, all times appear shifted 3 hours. Many thanks confirming that this is a bug and you are fixing it.
Gabriel Torres Posted November 27, 2019 Posted November 27, 2019 @Stuart Silvester The patch made available running the support tool fixed the default date fields, however the bug is still present in custom date fields. I opened a ticket explaining this in more detail.
Stuart Silvester Posted November 27, 2019 Posted November 27, 2019 43 minutes ago, Gabriel Torres said: @Stuart Silvester The patch made available running the support tool fixed the default date fields, however the bug is still present in custom date fields. I opened a ticket explaining this in more detail. The patch reverts the entire change for the Date field, the functionality of it will be identical to 4.4.8. Obviously, the issue it was attempting to fix will have been re-introduced however it was more of a niche issue than the fix was causing. We'll be revisiting the change for a future release and we'll also take a look at your ticket.
Gabriel Torres Posted November 27, 2019 Posted November 27, 2019 @Stuart Silvester It was a caching issue here... LOL Running the support tool a second time fixed it. Many thanks for your prompt reply.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.