TYPO3 Core

Digging deeper, I found out that TYPO3/CMS/Backend/FormEngineValidation is converting the year into positive year already inside FormEngineValidation.updateInputField.

When faking and overwriting the values in this method, moment js will still format the year as positive year.

we've finally fixed this in TYPO3 v12. With type=datetime (and even better with dbType=date and format=date) this works just fine, tested this just now. https://docs.typo3.org/m/typo3/reference-tca/12.4/en-us/ColumnsConfig/Type/Datetime/Index.html

If you feel this is still an issue in TYPO3 v12, let me know, and I will-re-open the issue.

I currently can't make this work in v12.
MySQL already states it can't handle dates prior year 1000: https://dev.mysql.com/doc/refman/8.0/en/datetime.html

The DATE type is used for values with a date part but no time part. MySQL retrieves and displays DATE values in 'YYYY-MM-DD' format. The supported range is '1000-01-01' to '9999-12-31'.

Also the JS doesn't allow me to select older dates. It works fine until 1970, but older dates behave strange. E.g. I could insert Year 100, but counting down ends up in 1999. Negative years are even ignored within the date picker.

Tested with v12.4.10.

I used the following TCA (with auto generated sql):

        'date' => [
            'exclude' => 0,
            'label' => $languageFile . '.date',
            'config' => [
                'type' => 'datetime',
                'format' => 'date',
                'dbType' => 'date',
                'required' => true,
            ],
        ],

I am closing this bug; the datepicker in v12 and v13 does work with dates down to "1000". For this to work though it is vital that the date TCA is either set to format=date (and using bigint signed as type), or format=Date+dbType=date (using native "date") field. In both cases entering a date like "02-06-1030" works here.

Theoretically the flatpickr (JS datepicker) should be able to also pick dates before "1000". However I believe because TYPO3 formats the date as "d-m-Y" (actually, dd-MM-yyyy) instead of "Y-m-d" there is some kind of mismatch here. The flatpickr demo itself can actually handle dates lower than 1000, but in TYPO3 context the cut-off seems to be "1000". Probably because "yyyy" no longer matches "yyy" (3 digits).

I would like to close this issue in favor of #104309 because I know Andreas is currently knee-deep in this; and if this is salvageable, I'm hoping this is where it gets addressed for.

If you believe closing this issue is a wronhg decision, please let me know.