Actions
Bug #94711
closedDate input with lower range inserts value even if no value is set since TYPO3 10.4.18
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2021-08-04
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
In some of our own extensions the fields starttime and endtime with a lower value for range:
'starttime' => array( 'exclude' => 1, 'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.starttime', 'config' => array( 'type' => 'input', 'renderType' => 'inputDateTime', 'size' => 13, 'eval' => 'datetime', 'default' => 0, 'range' => array( 'lower' => mktime(0, 0, 0, date('m'), date('d'), date('Y')) ), 'behaviour' => array( 'allowLanguageSynchronization' => true, ), ), ),
Until TYPO3 10.4.17 when we create new records, the starttime and endtime is empty after save. Since TYPO3 10.4.18 the current date is inserted in both fields after save, allthough the fields were empty.
Actions