[TYPO3-dev] Datetime bug in 4.2

[Steffen Kamper]

"Dmitry Dulepov [typo3]" <dmitry at typo3.org> schrieb im Newsbeitrag 
news:mailman.1.1203671122.3766.typo3-dev at lists.netfielders.de...
> Hi!
>
> Steffen Kamper wrote:
>> The idea was another. Dates should be displayed (BE) in the server 
>> timezone (or the timezone you configure for it). To achieve that times 
>> has to be stored in UTC and calculated by offset when display.
>> I think this whole handling is correct but just unfinished, eg there is 
>> no display which timezone is relevant.
>
> Hey, and how many extension developers take that into account? I do not 
> remember announcing such thing to the community. Most extensions just use 
> time()!
>
correct. That's why i said it's unfinished ;-)

>> I cite myself with a simple example:
>> a page shall be visible on a certain day at 8:00 am, the page is in one 
>> language and in zone UTC+1 and everyone expect this to be visible 8:00 am 
>> UTC +1.
>> One editor working in UTC-1. What should he enter to have correct 
>> behaviour?
>
> Time in server's timezone. He works on a server, so he must work with 
> server's time. He must enter 8:00 because this is the time that server 
> shows to users. If I live in UTC-10, I still just enter 8:00 because 
> everyting is dated by server time. Just think about it: you boss from 
> overseas says that article must appear at 8:00 his time. You know he runs 
> that server. So you just put 8:00 his time and you do not bother anymore. 
> There can be different use cases but this sounds the most typical to me.
>

don't forget the javascript - it's executed in your browser and use your 
timezone, not the servers.This javascript does the on-the-fly-calculation. 
So there are two possibilities:
1) js has a var with server's timezone and use it for calculate
2) jy uses utc and server does the calculate (but this is only visible after 
update)

vg  Steffen