#105549Replace fake UTC0 ISO8601 date strings by unqualified (local) ISO8601
Description
Goal is to align DataHandler to
- accept unqualified ISO8601 and interpret that as server localtime (which is currently faked using a UTC0 that is actually interpreted as unqualified localtime)
- support datetime offsets for persistence, for DataHanlder-as-a-API usage, without “unexpected” results (that we’ve seen reports for in the past)
Reviews 13
- main 86925[TASK] Transform all dates in DatabaseRowDateTimeFields to DateTime
- 13.4 89814[BUGFIX] Account for fake UTC-0 datetime strings in readonly elements
- 12.4 89867[BUGFIX] Account for fake UTC-0 datetime strings in readonly elements
- main 89192[BUGFIX] Respect 0 as valid empty value for non-nullable datetime fields
- main 89130[BUGFIX] Do not mangle integer datetime values during import
- main 89048[BUGFIX] Fix datetime default value inflation with default=0
- main 86888[!!!][FEATURE] Support qualified and unqualified ISO8601 in DataHandler
- 12.4 87122[TASK] Add functional DataHandler tests for type=datetime
- 13.4 87133[TASK] Add functional DataHandler tests for type=datetime
- main 87102[TASK] Add functional DataHandler tests for type=datetime
- 12.4 87008[BUGFIX] Fix rendering of native datetime fields as record title
- 13.4 87012[BUGFIX] Fix rendering of native datetime fields as record title
- main 86917[BUGFIX] Fix rendering of native datetime fields as record title
Related issues 6
- Task #104309Use ISO dates in FormEngine date handling
- Task #105643Transform all dates in DatabaseRowDateTimeFields to DateTime
- Task #105661Add functional DataHandler tests for type=datetime
- Bug #106364DatetimeElement stores format=time in seconds, while extbase interprets it as timezone-offset-mapped UTC timestamp, when php timezone is not UTC
- Bug #1065951970-01-01 in tt_content.date field after translation with date field disabled for editors
- Bug #106937TCA Datetime with different outputs depending on the “readonly” status