[TYPO3-dev] Datetime bug in 4.2 - SOLUTION
Steffen Kamper
steffen at sk-typo3.de
Fri May 23 22:16:03 CEST 2008
"lee perry" <leeperry at slack.de> schrieb im Newsbeitrag
news:mailman.1.1211565472.25487.typo3-dev at lists.netfielders.de...
>>> heya,
>>>
>>> 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...
>
>
> greetings,
> lee
Hi lee,
seems that you discovered a new bug with translation.
Could you open a new BT-entry with this description?
vg Steffen
More information about the TYPO3-dev
mailing list