#104309Use ISO dates in FormEngine date handling
Description
FormEngine’s date(time) validation is somewhat special. The format/parse process takes an arbitrary value and, if possible, converts this to a timestamp OR a hardcoded date/time format. It also incorporates a “poor-mans ISO format checks” to parse such dates explicitly.
This MUST go and FormEngine should always handle with UTC. It’s part of the date picker component to handle this.
Reviews 11
- main 86888[!!!][FEATURE] Support qualified and unqualified ISO8601 in DataHandler
- 12.4 87068[BUGFIX] Add FormEngine transformation for dbType=datetime in flexforms
- 13.4 87067[BUGFIX] Add FormEngine transformation for dbType=datetime in flexforms
- main 86912[BUGFIX] Add FormEngine transformation for dbType=datetime in flexforms
- 12.4 86830[BUGFIX] Validate date ranges correctly
- 13.4 86836[BUGFIX] Validate date ranges correctly
- main 86730[BUGFIX] Validate date ranges correctly
- 12.4 85469[BUGFIX] Apply configured date format to date(time) fields
- main 84880[BUGFIX] Apply configured date format to date(time) fields
- 12.4 85243[TASK] Use ISO8601 dates in FormEngine datetime handling
- main 84902[TASK] Use ISO8601 dates in FormEngine datetime handling
Related issues 6
- Feature #61110Support for timezones in all date fields in TYPO3 BE
- Bug #91508It is not possible to save "negative" dates, e.g. a year before jesus christus with date inputs
- Bug #105430Date validation in FormEngine broken
- Feature #105549Replace fake UTC0 ISO8601 date strings by unqualified (local) ISO8601
- Bug #106364DatetimeElement stores format=time in seconds, while extbase interprets it as timezone-offset-mapped UTC timestamp, when php timezone is not UTC
- Bug #107024Translated starttime and endtime fields not editable [regression]