Replies: 3 comments 1 reply
-
It's probably because in Edit: Had to also edit flatpickr format on line 135 to |
Beta Was this translation helpful? Give feedback.
-
The offset is intended to improve the user experience. Dates should always be stored in UTC in the database, but you don't want your users to have to do mental gymnastics with timezones when using date and time pickers in the CMS. Are you reporting a bug with this implementation, or is it more that you were looking to disable that behavior? |
Beta Was this translation helpful? Give feedback.
-
To be honest, at the point when I opened this issue I was completely oblivious to the fact that it was good practice to store UTC dates in the DB - answering your question - it's not a bug if you followed best practices, so we might as well close this. But still it would be nice to be able to store and display datetime values independently from timezones. Do you have an idea if it would be possible currently? |
Beta Was this translation helpful? Give feedback.
-
Description
time_picker
field would adjust the value displayed in the field based on OS/browser timezone ie. will not display the value stored in the DB, but treats that value as if it was UTC and the displayed value was local. Value in store is correct so it should be something related to frontend/flatpickr.js.Edit:
date_picker
with time is also affected.Steps to reproduce
Set your OS timezone to something other than UTC and compare DB stored value and the field.
Expected result
No timezone adjustment
Actual result
Value in field offset by timezone
Versions
Twill version: 2.3.0
Laravel version: 10
Beta Was this translation helpful? Give feedback.
All reactions