Epic #77562

Misbehaviors with datetime values and timezones

Added by Oliver Hader about 5 years ago. Updated 9 months ago.

Status:
Accepted
Priority:
Could have
Assignee:
-
Category:
DataHandler aka TCEmain
Start date:
2012-05-17
Due date:
% Done:

61%

Estimated time:
(Total: 0.00 h)
Sprint Focus:
Stabilization Sprint

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

TYPO3 datetime evaluation.pdf (361 KB) TYPO3 datetime evaluation.pdf Markus Klein, 2017-06-06 18:20
TYPO3 datetime evaluation.pdf (367 KB) TYPO3 datetime evaluation.pdf Markus Klein, 2017-06-07 14:12
datetimetest.zip (11.4 KB) datetimetest.zip Test extension Markus Klein, 2017-06-08 02:40

Subtasks

Bug #37244: TCA date evaluation for dates lower 01-01-1970 failsClosed2012-05-17

Actions
Bug #68651: Datetime() properties have wrong timezoneAcceptedAndreas Wolf2015-07-30

Actions
Feature #61110: Support for timezones in all date fields in TYPO3 BENew2014-08-21

Actions
Bug #63482: Query constraint on a DateTime field with a DateTime argument should trigger date formatNew2014-12-01

Actions
Feature #64372: Add timezone-handling for value-display depending on FE-userNeeds Feedback2015-01-20

Actions
Bug #66435: Scheduler Task - Cron Command for recurring tasks not evaluated correctlyClosed2015-04-15

Actions
Bug #66793: "simulate time" in admin-panel does not respect timezoneClosed2015-05-05

Actions
Bug #69290: Dates get reduced by a day if before 1970Closed2015-08-24

Actions
Feature #72053: Extbase: Support \DateTimeInterface instead of \DateTimeClosed2015-12-04

Actions
Bug #73637: Extbase DateTimeConverter cannot handle negative timestampsClosed2016-02-23

Actions
Bug #77563: Native DBMS datetime columns are not handled correctlyClosed2016-08-21

Actions
Bug #78251: Not possible to output DateTime by TSRejected2016-10-12

Actions
Task #78471: Acceptance test for DatepickerClosedDaniel Lorenz2016-10-27

Actions
Bug #79197: There should be ISO Date Format Year-Month-DayClosedMarkus Klein2017-01-08

Actions
Bug #79249: TCA fields with eval types "time" or "timesec" are incorrectly stored in the databaseClosedMarkus Klein2017-01-10

Actions
Bug #79304: SQL error if empty datetime value is savedClosedSascha Egerer2017-01-12

Actions
Bug #79448: Handling dates in the very past inside T3-BackendNew2017-01-24

Actions
Bug #79557: Date fields DataMapper handling problemNew2017-01-30

Actions
Bug #79613: Saving wrong Date into DB if Field is of type DATENew2017-02-03

Actions
Bug #80349: Extbase mapping of \DateTime for integer values does not set timezone with region string but only offsetNew2017-03-20

Actions
Bug #81228: l10n_mode exclude doesn't work correctly for timestamp fieldsClosed2017-05-15

Actions
Bug #81719: DateTime comparisons not possible in 8.7New2017-06-27

Actions
Bug #81940: FE_USER Access Stop DateClosed2017-07-21

Actions
Bug #82126: EXT:belog - Error when using a custom timeframe Closed2017-08-17

Actions
Bug #91240: Extbase DateTime with native dbType=datetime converts output differentlyClosedBenni Mack2020-04-30

Actions
Bug #91508: It is not possible to save "negative" dates, e.g. a year before jesus christus with date inputsNew2020-05-27

Actions

Related issues

Related to TYPO3 Core - Feature #51844: Fix date-format in edit-view of a recordAcceptedJo Hasenau2013-09-09

Actions
Related to TYPO3 Core - Bug #85602: The date and time are wrong in the log module viewNew2018-07-20

Actions
Has duplicate TYPO3 Core - Bug #81489: Major time and date handling issues in BEClosed2017-01-12

Actions
#1

Updated by Mona Muzaffar over 4 years ago

  • Related to Epic #80852: Datetime handling in backend added
#2

Updated by Markus Klein over 4 years ago

  • Has duplicate Bug #81489: Major time and date handling issues in BE added
#4

Updated by Markus Klein over 4 years ago

  • Description updated (diff)
  • Status changed from New to Accepted
  • Complexity set to medium
#5

Updated by Markus Klein over 4 years ago

  • Description updated (diff)
#6

Updated by Riccardo De Contardi over 4 years ago

  • Related to deleted (Epic #80852: Datetime handling in backend)
#7

Updated by Riccardo De Contardi over 4 years ago

  • Tracker changed from Bug to Epic
#8

Updated by Markus Klein over 4 years ago

#9

Updated by Markus Klein over 4 years ago

  • Tracker changed from Bug to Epic
  • Target version set to next-patchlevel
  • Sprint Focus set to Stabilization Sprint
#10

Updated by Markus Klein over 4 years ago

  • File deleted (datetimetest.zip)
#12

Updated by Susanne Moog over 3 years ago

  • Related to Feature #51844: Fix date-format in edit-view of a record added
#13

Updated by David Bruchmann about 3 years ago

  • Related to Bug #85602: The date and time are wrong in the log module view added
#14

Updated by Benni Mack over 2 years ago

  • Category changed from Miscellaneous to DataHandler aka TCEmain
#15

Updated by Benni Mack over 2 years ago

  • Target version changed from next-patchlevel to Candidate for patchlevel
#16

Updated by Christoph Dörfel over 2 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.

#17

Updated by Susanne Moog over 2 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.

Also available in: Atom PDF