TYPO3 Core

Benjamin Kluge wrote:

In issue https://forge.typo3.org/issues/81940 are TCA range upper removed. But in file typo3/sysext/backend/Resources/Public/JavaScript/FormEngineValidation.js in method FormEngineValidation.parseDate are fix the year 2038 included.

At the moment you cant typing a date bigger than year 2038 in datime fields, please remove this limitation. It set always the value to the today date

I think it's a problem with unix timestamps, see for example #16735 and https://en.wikipedia.org/wiki/Year_2038_problem

Wittkiel Gruppe wrote:

I think it's a problem with unix timestamps, see for example #16735 and https://en.wikipedia.org/wiki/Year_2038_problem

But I think that is not existing anymore in Javascript or mysql (https://bugs.mysql.com/bug.php?id=12654), and also in php (i think)

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54488