Epic #77562
openMisbehaviors with datetime values and timezones
76%
Description
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
Files
Updated by Mona Muzaffar over 7 years ago
- Related to Epic #80852: Datetime handling in backend added
Updated by Markus Klein over 7 years ago
- Has duplicate Bug #81489: Major time and date handling issues in BE added
Updated by Markus Klein over 7 years ago
Updated by Markus Klein over 7 years ago
- Description updated (diff)
- Status changed from New to Accepted
- Complexity set to medium
Updated by Riccardo De Contardi over 7 years ago
- Related to deleted (Epic #80852: Datetime handling in backend)
Updated by Riccardo De Contardi over 7 years ago
- Tracker changed from Bug to Epic
Updated by Markus Klein over 7 years ago
- File TYPO3 datetime evaluation.pdf TYPO3 datetime evaluation.pdf added
- File datetimetest.zip added
- Tracker changed from Epic to Bug
- TYPO3 Version set to 7
- PHP Version set to 5.5
- Complexity set to medium
- Is Regression set to No
Updated by Markus Klein over 7 years ago
- Tracker changed from Bug to Epic
- Target version set to next-patchlevel
- Sprint Focus set to Stabilization Sprint
Updated by Markus Klein over 7 years ago
- File datetimetest.zip datetimetest.zip added
Updated by Susanne Moog almost 7 years ago
- Related to Feature #51844: Fix date-format in edit-view of a record added
Updated by David Bruchmann over 6 years ago
- Related to Bug #85602: The date and time are wrong in the log module view added
Updated by Benni Mack over 5 years ago
- Category changed from Miscellaneous to DataHandler aka TCEmain
Updated by Benni Mack over 5 years ago
- Target version changed from next-patchlevel to Candidate for patchlevel
Updated by Christoph Dörfel over 5 years 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:
https://codeblog.jonskeet.uk/2019/03/27/storing-utc-is-not-a-silver-bullet/
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.
Updated by Susanne Moog over 5 years 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.
Updated by Benni Mack over 1 year ago
- Sprint Focus deleted (
Stabilization Sprint)
Updated by Georg Ringer 6 months ago
- Has duplicate Bug #102087: Backend user need a own timezone added