#80559datetime and time handling should always have timezone information
Description
each input or output should be able to handle timezones.
so an editor might enter a time and his local timezone must be respected before the time is stored as UTC in the DB. (not every editor is capable to calculate UTC time from local time)
so a setting for the timezone of the user is needed (User settings)
and also every time /datetime field should have its own timezone field (preset with user settings) so an editor also can enter data for other timezones.
so the input could be saved in a clean way as UTC.
for output (or visibilty checks) the server timezone could be default, but might be set in a viewhelper, typoscript or php for generating output for other locations.
maybe a special setting ‘visitor’ to render the time depending on visitors location (if that information is available)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 5
- Feature #64372Add timezone-handling for value-display depending on FE-user
- Bug #66793"simulate time" in admin-panel does not respect timezone
- Bug #68651Datetime() properties have wrong timezone
- Bug #79613Saving wrong Date into DB if Field is of type DATE
- Bug #80349Extbase mapping of \DateTime for integer values does not set timezone with region string but only offset