[TYPO3-core] RFC: Bug #1697: Datetime input fields and timezone shift bug
Steffen Kamper
steffen at sk-typo3.de
Tue Oct 23 23:12:47 CEST 2007
"Martin Kutschker" <martin.kutschker-n0spam at no5pam-blackbox.net> schrieb im
Newsbeitrag
news:mailman.1.1193171729.14266.typo3-team-core at lists.netfielders.de...
> Steffen Kamper schrieb:
>> "Ingo Renner" <ingo at typo3.org> schrieb im Newsbeitrag
>> news:mailman.1.1193155659.27713.typo3-team-core at lists.netfielders.de...
>>> Ingo Renner wrote:
>>>
>>>>> Also remember that there is a Conf-Var, that was never used:
>>>>> $TYPO3_CONF_VARS['SYS']['serverTimeZone']
>>>>> This is a possibility to read the server TZ.
>>>> to calculate everything else ...
>>> BTW: this is also a case for "only care for the BE, don't care for the
>>> FE" as in the FE the extensions are responsible to render things
>>> right... which makes things a lot easier.
>>
>> absolutely.
>> It would be also possible to store the beuser TZ in BE_USER-Object after
>> login, where client TZ could be transferred easy.
>
> Not quite. The BE_USER object is created for every script, it's not
> serialzed anywhere (a point for improvement?), but we can use the session
> table for that.
>
> Masi
session will be fine.
We should also think about JS and login.
Ok, atm login without JS is impossible, this should be changed anyway.
So if there is no JS we have to look to server vars, if nothing is available
server settings should be used - just to keep that in mind.
vg Steffen
More information about the TYPO3-team-core
mailing list