[TYPO3-dev] Datetime bug in 4.2 - SOLUTION

[Martin Kutschker]

Dmitry Dulepov [typo3] schrieb:
> Hi!
> 
> Steffen Ritter wrote:
>> as far as I got your text problems last of point 2 and the getUTC 
>> function.
>> So why cut whole processing. Point to I think it's a sign problem, so 
>> add *-1 to the timezone-"summand".
> 
> Do you think I did not try? I spent 8 hours on it. The logic is broken 
> there. If you look into it in the debuggger, you will understand why: 
> information about user timezone is not known to server. The time value, 
> which is sent to server, is neither UTC, no server timezone.

Ok, ok I didn't test it. But wasn't it the original idea to send UTC from 
the BE client to the server? If it were (this part seems to be broken), the 
server could change it into his TZ and store the time correctly. *

Masi

* That is, if we assume that any editor will always enter times in her TZ. 
Whether this is true or not could be defined by pageTS/userTS. Possible 
options are: UTC, server TZ, client TZ. It doesn't matter if the storage 
format on the server is local TZ (as it is now) or UTC (which could be an 
option for 4.3). It only matters that the time sent from and to the client 
is always UTC. As for FE extensions: they have - as this "defined" by the 
Core - to make sure that the time that goes into the DB is local time. How 
they handle input/output is up to them (and is probably dependent on te 
wishes and needs of the site owner).