Keystone-classic: Timestamps appear differently in Admin UI

[ddaddy]

I have a user field set to DateTime like this
createdAt: { type: Types.Datetime, default: Date.now },

and when viewed in the admin User list a record appears like this:

yet when I click the user, it shows a different time like this:

The actual timestamp in the db is:
"createdAt" : ISODate("2016-06-15T23:26:32Z"),

[jstockwin]

I think this may be a duplicate of #1487 and/or #1345. Perhaps it was fixed in master but not 0.3?

[ddaddy]

Yes they look the same. And although marked Critical, it's still not fixed in 3.19

[ddaddy]

And just to confirm, it also saves a new time in the field when any changes are made to the record, which is a serious bug.

[mxstbr]

Perhaps it was fixed in master but not 0.3?

@JedWatson will know more about that, any input here?

[JedWatson]

I _swear_ we've fixed this one before. Really need to work out how to set up some unit tests that test for the server and client being in different timezones, I suspect this came back with a PR or something. It's _way_ to easy to miss for such a critical bug.

@mxstbr no input other than that we need to get on this and patch 0.3 with a fix

[ddaddy]

Did a patch for this ever get done?
Whenever I make changes to an object via the admin panel, it always fires my code that checks for a date field being new, even when it hasn't been changed, because the admin panel changes the current saved time by an hour.

[ttsirkia]

It was fixed in #2894 but only for 0.4. There are two open (possibly outdated) pull requests for 0.3 that were never merged.

[dijs]

I am also seeing inconsistencies in datetimes before and after saving. It would be amazing to get a fix.

Currently we are having to save our time's correctly by adding 5 hours to them...

[dijs]

Any progress here?

[mxstbr]

Sorry, we're very very focussed on getting v4 finished at the moment, (beta release this/next week hopefully) so no progress so far.

[mollfrey]

Argh. Just ran into this. Running v0.3.17
Any hope for a merge soon?

I believe the two related pull requests are #1605 and #1445

[waltonryan]

Ran into this issue as well. Any temporary fix we could do on our side before the fix is merged?

[ValeriyDevPro]

This is not funny, timezone issue is the critical bug. I do not understand why stable version did not get this fix yet, but unstable version 0.4 has that?
Every time I'm saving item with Date it shifts to +2h. I can't handle that at all, hooks in mongoose did not catch that Date was set up by user. Any workaround?

[dijs]

Any updates on timezone issues yet?

[Noviny]

I talked about this in #3012. The resolution is we are releasing one final version of 3 that resolves this, though note we will not be supporting 3 after this final patch. We recommend upgrading, for which you can find a guide here