You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently many (= most?) datetime fields are stored in the DB in the user's timezone as set in their J! account or, if set to "default" there or if it's a guest in the frontend, in J!'s global system timezone.
That's a big no-no, typically messing up both backend and frontend display, add/edit etc etc, basically J!'s native time system.
In the database, all datetime fields must be stored in UTC time. Always and everywhere, no matter set system or user timezones.
Currently many (= most?) datetime fields are stored in the DB in the user's timezone as set in their J! account or, if set to "default" there or if it's a guest in the frontend, in J!'s global system timezone.
That's a big no-no, typically messing up both backend and frontend display, add/edit etc etc, basically J!'s native time system.
In the database, all datetime fields must be stored in UTC time. Always and everywhere, no matter set system or user timezones.
Also see https://www.joomlaworks.net/forum/k2-en/63669-the-timezone-conundrum
The text was updated successfully, but these errors were encountered: