[TYPO3-core] RFC #13250: Bug: Translation handling for IRRE combo records broken

[Marcel Greter]

Hi Susanne,

First of all thanks for your response.

As you might see my patch has two corrections. The second one really is a no brainer as $languageField (Line 1140) is never assigned a value (the actual variable is called $parentLanguageField).

Have you had a look at http://www.olly.de/typo3/irre_localization.html at 2:22 mins ?
There you can see the bug I meant. At the top you can see that the record being edited is german but the new created relation (the offer with [no title]) is of default language (but should be german too, IMO). Here's a screenshot for better explanation: http://bayimg.com/oAlBpAACO

I was able to reproduce it by doing the same steps as showed in the video/slideshow I mentioned. My patch should fix that problem. Do you have another bug or does it not work for you with this patch for this case? If so I will check my patch again against newest revision.

Regards,
Marcel Greter


On Apr 11, 2010, at 9:56 AM, Susanne Moog wrote:

> Hi Marcel,
> 
> On 08.03.2010 15:02, Marcel Greter wrote:
>> This is an SVN patch request.
>> 
>> Type: Bugfix
>> 
>> Bugtracker references:
>> http://bugs.typo3.org/view.php?id=13250
>> 
>> Branches:
>> Trunk - Revision 7088
>> 
>> Problem:
>> LanguageTranslation broken when using IRRE combo Records.
>> See Bugtracker for a better explanation/example.
>> 
>> Solution:
>> 1. renderCombinationTable did not set language for new records
>> 2. createNewRecord had a typo: $languageField instead of $parentLanguageField
> 
> first of all, thank you for your patch. However I am unable to reproduce
> the mentioned behavior - or more to the point, I can reproduce something
> that looks very much like your bug description, but it's not fixed with
> your patch.
> 
> Could you perhaps provide a step-by-step reproduce/test guide?
> 
>