TYPO3 Core

I've same problem.

The date is correctly stored in the database.
At viewing in BE form of value output is false.

I think the problem is at render the dbType field.

I fix the problem in typo3\sysext\backend\Classes\Form\DataPreprocessor.php
function renderRecord with change line 199
$row[$column] = !empty($row[$column]) && $row[$column] !== $emptyValue ? strtotime($row[$column]) : 0;
to
$row[$column] = !empty($row[$column]) && $row[$column] !== $emptyValue ? strtotime($row[$column] . ' GMT') : 0;

so, the strtotime function return a timestamp with GMT time and not local timezone.

I hope it's helpful patch

Thanks for digging a bit in the issue.

I think the general approach has to be more complicated as the solution might work for you in GMT-timezone but the general fallback timezone is UTC if nothing is configured in php.ini.

Having verified the functions in adodb-time.php I remarked a special issue by executing the tests and I think the result might concern php in general perhaps and therefore TYPO3 too:

Having adjusted the timezone to Europe/Berlin and executing the tests there is one long formatted string echoed two times and the results for that time differ because the timezone seems being converted internally once to CET and once to CEST:

date CET 1970-01-01 01:00:00 am AM 01 Thu January 1 1 01 01 00 1 Thursday 0 01 Jan 1 +0100 RFC2822 Thu, 01 Jan 1970 01:00:00 +0100 00 31 0 4 70 1970 0 3600 2003

date CEST 1970-01-01 01:00:00 am AM 01 Thu January 1 1 01 01 00 1 Thursday 0 01 Jan 1 +0100 RFC2822 Thu, 01 Jan 1970 01:00:00 +0100 00 31 0 4 70 1970 0 3600 2003

More about this bug can be found here, till now I never verified why that happens exactly:
https://github.com/ADOdb/ADOdb/issues/144

Apart from that a different timezone shouldn't be a reason usually that a whole day is missing, I'd expect 1 or a few hours maximum.

Nevertheless, I'll try your solution and think a bit how to track it down more precisely.

The problem here is that the date gets transformed from a timestamp to a date and back. During this it can happen that an hour or two are subtracted giving you a date/time on the day before. The time is then stripped, which gives you the day before at midnight. The same happens on each subsequent save.

PS: There was hope that with UTC-timehandling to land in TYPO3 CMS 7 this might be solved. However it's quite certain that won't make it into CMS 7 anymore. So we need a regular bugfix here for the existing environment.

I tried using EXT:news and its field "Date & Time", filling it with: "00:00 06-09-1969"

and the date has been saved correclty, both for TYPO3 7.6.22 and 8.7.5

Do you think it is sufficient to consider this closed or a different test should be made? Thank you.