Misbehaviors with datetime values and timezones
This issue serves as an umbrella collector.
We can do little to fix stuff in v7, but we shall fix a lot in v8.
The goals for v8 are:
- Same DB content as in v7
- Values written to FormEngine must contain the server's timezone in the ISO-format
- FormEngine JS must be aware of the timezone used in BE to write back correct values
#16 Updated by Christoph Dörfel about 1 year ago
Since you're updating bug tickets where some of them are already over 3 years old (https://forge.typo3.org/issues/68651) and finally consider tackling this issue, maybe it would be worth looking at all the issues with dates and time zones, especially when saving dates for future events:
This article is for C# but explains that it might not be enough to just save an ISO 8601 representation of the datetime. Time zone rules can change over time and existing dates in the future have to be updated accordingly. Just FYI.
#17 Updated by Susanne Moog about 1 year ago
Thanks for the comment and the link. Basically we are lacking the people to tackle this issue in a broad scope currently (afaik) - if you want to get involved (or know of people interested in helping out) please feel free to join #typo3-cms-coredev on slack - else I'm not seeing any quick fixes on this topic at this point in time.