Bug #81228

Epic #77562: Misbehaviors with datetime values and timezones

l10n_mode exclude doesn't work correctly for timestamp fields

Added by Markus no-lastname-given almost 4 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-05-15
Due date:
% Done:

0%

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

Description

In TYPO3 8.7.1 I have the following TCA:

'date' => [
'exclude' => true,
'l10n_mode' => 'exclude',
'l10n_display' => 'defaultAsReadonly',
'label' => 'Date',
'config' => [
'type' => 'input',
'eval' => 'date',
'disableAgeDisplay' => 1,
'default' => time()
],
],

The system is set to German as default and English as secondary language.

Now when I edit the record in TYPO3 backend and save the date in German, it is correctly set for the English record as well - BUT when I edit the English record (where I can't set the date, because the field is set to "defaultAsReadonly"), the date for the English record is changed to one day before after/on save. The German Record remains unchanged. The behaviour doesn't seem to be connected to the l10n_display setting; if it is ommited, the field is not displayed, but nevertheless changed on save.

Also available in: Atom PDF