Bug #79448

Epic #77562: Misbehaviors with datetime values and timezones

Handling dates in the very past inside T3-Backend

Added by Ralle Büchnitz over 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2017-01-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I tried to store a date around 01.01.1800 in T3-Backend.

I wrote an extension but saving fails each time - as the date is not stored correctly.

I can't even say how T3 determines/converts the date. As the system stores something around 1936. Seems like some sort of converting error in T3-Backend. Same with dates in the very future.

If i set the 'date' field directly in the database to the correct date it won't be displayed at all.

Here are some additional informations:

\ext_tables.sql
geboren_am date DEFAULT '0000-00-00',

Configuration\TCA\mymodel.php
'geboren_am' => array(
'exclude' => 1,
'label' => geboren_am',
'config' => array(
'dbType' => 'date',
'type' => 'input',
'size' => 13,
'max' => 20,
'eval' => 'date',
'checkbox' => 0,
'default' => '0000-00-00'
),
),


Related issues

Related to TYPO3 Core - Bug #69287: Can't enter years before 1902 in date-fieldsClosed2015-08-24

Actions
Related to TYPO3 Core - Bug #37244: TCA date evaluation for dates lower 01-01-1970 failsClosed2012-05-17

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

Actions

Also available in: Atom PDF