Skip to content
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

peterboorsma opened this issue Jun 30, 2020 · 4 comments · Fixed by #1593 or #1901

Unexpected time notation/behaviour #1581

peterboorsma opened this issue Jun 30, 2020 · 4 comments · Fixed by #1593 or #1901


Copy link

@peterboorsma peterboorsma commented Jun 30, 2020

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.

Screenshot 2020-06-30 at 13 05 00

When creating a record, the timestamp is of by +2 hours.

Local time:
Screenshot 2020-06-30 at 13 07 30

Saving a new record:
Screenshot 2020-06-30 at 13 07 22

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

Copy link
Contributor Author

@peterboorsma peterboorsma commented Aug 21, 2020

I'm reopening this. The problem still occurs. Tested it on multiple sites, on my local MAMP as well as a public server.

Server time:
Screenshot 2020-08-21 at 09 03 28

Time in Bolt:
Screenshot 2020-08-21 at 09 02 59

PHP Version 7.3.20
Bolt 4.0.0 RC35

@peterboorsma peterboorsma reopened this Aug 21, 2020
Copy link

@sellmark sellmark commented Aug 25, 2020

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.
Not a resolve, but may make u to look somewhere you wouldn't look normally :)

Copy link

@bobdenotter bobdenotter commented Aug 25, 2020

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.

Copy link

@I-Valchev I-Valchev commented Aug 28, 2020

This definitely needs fixing, but letss bump it to 4.1 if we can't solve it earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
4 participants