[TYPO3-dev] Datetime bug in 4.2 - SOLUTION
Ernesto Baschny [cron IT]
ernst at cron-it.de
Mon May 26 17:43:31 CEST 2008
Hi Lee,
lee perry wrote: on 23.05.2008 19:59:
>>> is there any result of the dialogue between Dmitry and Ernesto,
>>> because I'm working with TYPO3 4.2 and I can see the problem isn't
>>> solved yet - or can I find a solution of this datetime bug?
>>>
>>> thanx and greetings,
>>> lee
>> Hi,
>> the problem is solved in 4.2.
>> If you encounter any problem, can you describe exactly where you have
>> it, how to reproduce?
>>
>> vg Steffen
>>
>
> Hi Steffen,
>
> I'm working with the final version of TYPO3 4.2 and I have a field in
> one of my own extension with a datetime:
>
> "datetime" => Array (
> "exclude" => 1,
> "label" =>
> "LLL:EXT:my_lawyer_management/locallang_db.xml:tx_mylawyermanagement_newsletterissues.datetime",
>
> "config" => Array (
> "type" => "input",
> "size" => "8",
> "max" => "20",
> "eval" => "date",
> "checkbox" => "0",
> )
> ),
>
> When I save a date in my default language - the date is saved as
> timestamp in the database with the correct date and a time of midnight.
> When I translate this record the date should be get from the
> standard-language-record - it is taken, but with a time difference of 2
> hours in the past, so the date of the translated record is now from one
> day before.
>
> I'm working here in Berlin, Germany so with the summertime I have the 2
> hours difference...
Indeed this is a bug that only appears when you are localizing an
record. I could reproduce that.
Please submit the issue with your description to the bug tracker
(bugs.typo3.org) and give us the issue-id here on the list so we can
follow-up on that.
I will look into this ASAP.
Thanks lee!
Cheers,
Ernesto
More information about the TYPO3-dev
mailing list