[TYPO3-core] RFC: Bug #1697: Datetime input fields and timezone shift bug

[Ernesto Baschny [cron IT]]

Martin Kutschker wrote: on 23.10.2007 12:41:
> Ernesto Baschny [cron IT] schrieb:
>> Ingo Renner wrote: on 23.10.2007 12:25:
>>> Ingo Renner wrote:
>>>> Ernesto Baschny [cron IT] wrote:
>>>>
>>>>> Problem:
>>>>> Editing date, datetime, time and timesec fields in BE when you have an
>>>>> offset between your clients timezone and the server timezone leads to
>>>>> wrong information being stored.
>>>> What's the intended behavior?
>>> What I actually wanted/need to know is the expected outcome....
>>>
>>> I'm now running my local dev server in CEST and a virtual machine in
>>> Chicago time -6 hours or so.
>>>
>>> Now if I enter a time in Chicago, let's say 18:00, what should the list
>>> view in Chicago and CEST show?
>>
>> As we don't store any TZ information in date / datetime fields (they are
>> integers), you should always see 18h00 on any view (list view, backend
>> form, etc).
> 
> But in England (+0) I should see 0:00 (ie 24:00) according to my local
> time zone, right?


Yes, if you enter 0:00 you should see 0:00 in view>list, no matter where
you are. And especially: if you enter 2007-10-23 in a date field, it
should stay 2007-10-23 in view>list and not switch to 2007-10-22 or
2007-10-24.

Cheers,
Ernesto