Comment 4 for bug 1846750

We are still on Mahara Version 19.04.0 (2019031906) and we are still having this problem.

@Robert
SELECT @@global.time_zone, @@session.time_zone;
Output: SYSTEM/SYSTEM
SELECT TIMESTAMPDIFF(HOUR, UTC_TIMESTAMP(), NOW()) AS tz_offset;
Output: 2

"date" command on server shows:
Do 16. Jul 14:59:26 CEST 2020
This is the correct time here right now.

Infos about database: SHOW VARIABLES LIKE "%version%";

innodb_version: 5.5.61-MariaDB-38.13
protocol_version: 10
version: 5.5.65-MariaDB

Client OS: Windows 10 Enterprise 1909 (but also other Win10 non Enterprise and earlier Versions)

Browser:
Chrome Version 83.0.4103.97
Firefox 78.0.2
Microsoft Edge
(but also earlier Versions)

Like i said before:

This only happens when I select a date which is in winter time (Winterzeit MEZ/CET UTC+1)
It doesn' happen when I select a date which is in summer time (Sommerzeit MESZ/CEST UTC+2)

For example saving 2020/07/16 works correctly.
But saving 2020/11/16 ends up showing as 2020/11/15 after saving.