Issue Bug Closed

#79448Handling dates in the very past inside T3-Backend

Ralle Büchnitz 01/24/17, 18:09 updated 07/06/23, 11:41

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’
),
),

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.