[TYPO3-core] RFC #7626: Date/time handling is completely broken in 4.2
Martin Kutschker
martin.kutschker-n0spam at no5pam-blackbox.net
Fri Feb 22 22:33:38 CET 2008
Dmitry Dulepov [typo3] schrieb:
> Hi!
>
> Martin Kutschker wrote:
>> In the BE the time stays as entered, but in the DB it seems to be the
>> TZ of the client !?!? I have fiddled with my TZ setting of Windows and
>> restarted FF everytime. Or do I have to reboot?
>
> Welcome... You do not have to reboot, it will not help. It just works
> this way: you always get +TZ in the database. I wrote about that in the
> bug report and here in the list. Quoting with some omissions:
>
>> 0. ...Let's use $TIME for indication of current ~local~ time.
>> 2. jsfunc.tbe_editor.js ~substructs~ the value of "getTimezoneOffset()"
>> from $TIME and stores result in hidden form field. Value of
>> "getTimezoneOffset()" is "-2h" for UTC+2. Due to substruction we now
>> have $TIME+2h in the hidden form field...
>> 5. User saves the form
>> 6. Wrong value of $TIME+2 gets into the database.
>
> This is what I am trying to communicate all this time: VALUE IN THE
> DATABASE IS ALWAYS +CLIENT_TZ IN THE FUTURE! May be I am not saying it
> clear enough to show all seriousness of the problem...
Really odd, because sending UTC to the server cannot be that hard.
Masi
More information about the TYPO3-team-core
mailing list