-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected time notation/behaviour #1581
Comments
I'm just wondering - isn't that a Javascript related issue? It happened to me a lot of times when I read from DB(SQL) specific datetime and have it "transformed"(mostly +2h, because that's my locale) by invoking a Date object on the given value. |
It has to do with the time difference between UTC ("greenwich time") and your local time. Timestamps should be saved in the DB in UTC, and then in the application show up as local time. What we're seeing here is this transformation going wrong sometimes. We'll need to dig in how to fix it properly. |
This definitely needs fixing, but letss bump it to 4.1 if we can't solve it earlier. |
In the backend:
When saving a record, the 'current status' text below the save button shows "in 1 hour", instead of the time the record is changed/saved.
When creating a record, the timestamp is of by +2 hours.
Local time:
Saving a new record:
Addition to this issue: displayed time uses AM/PM notation instead of 24 hour clock. And the time notation always show in English instead of the used locale in the backend.
In my specific case date/time isn't being translated to NL in the frontend/templates. This is an older issue but forgot to make an issue. But it may be related.
Bolt 4.0.0 RC26 + RC25
The text was updated successfully, but these errors were encountered: