[TYPO3-core] RFC: Feature Request #6087: IRRE - Localization of child records

[Ingmar Schlecht]

Hi guys,

Olly and I just sat together and went through the patch as well as doing 
functionality testing.

We just discovered some issues with asymmetric m:n relations, but the 
most used case 1:n works nicely as expected.

Generally, this patch gets my +1, and Olly will come up with a follow up 
patch fixing the remaining issues during the next days.

cheers
Ingmar


Oliver Hader wrote:
> REMINDER RFC #6087
> Post-Review by a Core Developer required
> 
> 
> Michael Stucki schrieb:
>> Thank you! However, that was the one which is not reviewed yet, right?
>>
>> May I suggest that you mark this in the ChangeLog line? I think that's 
>> the
>> easiest way to make sure we'll not forget about it...
>>
>> - michael
>>
>> Oliver Hader wrote:
>>
>>> FYI: Committed to SVN Trunk (rev. 3042)
>>>
>>> olly
>>>
>>>
>>> Oliver Hader schrieb:
>>>> This is a SVN patch request.
>>>>
>>>> Problem:
>>>> The localization of child records when viewing the parent record isn't
>>>> possible. This is a missing feature of TYPO3 4.1.
>>>>
>>>> Solution:
>>>> Introduce some new TCA configuration settings which allow to define 
>>>> what
>>>> should happen to child records when a parent record gets localized (see
>>>> also attached text file for documentation changes).
>>>> Basically a new TCA property is introduced for fields of type 'inline'
>>>> with the name 'localizationMode' and can be set to 'keep' or 'select'.
>>>>
>>>> Mode *keep*:
>>>> This is not a real localization, since the children are taken from the
>>>> parent of the original language. But the children can be moved, 
>>>> deleted,
>>>> modified etc. on the localized parent which - of course - also affects
>>>> the original language.
>>>>     Mode *select*:
>>>> This mode provides the possibility to have an selective localization 
>>>> and
>>>> to compare localized data to the pendants of the original language.
>>>> Furthermore this mode is extended by a 'localize all' feature, which
>>>> works similar to the localization of content on pages, and a
>>>> 'synchronize' feature which offers the possibility to synchronize a
>>>> localization with its original language.
>>>>
>>>> Documentation changes:
>>>> -> see attached text file
>>>>
>>>> Comments:
>>>> This issue is related to IRRE but also to other parts of the Core. The
>>>> regular "I'll commit in one week if nobody objects" is not given here.
>>>> I introduced a new class t3lib_tca to start with a base for common TCA
>>>> related checks and to retrieve parts of the configuration. It makes
>>>> things a bit simpler but - to be honest - has not a real concept yet.
>>>> I'm looking forward also to conceptual comments on this. But I'm fine
>>>> with removing that class and put the checks into the old classes
>>>> (TCEmain, TCEforms, TCEforms_inline), since TYPO3 4.2.0-beta1 gets
>>>> pushed...
>>>>
>>>> Some days ago I've create a short screencast which show this feature:
>>>> http://www.olly.de/typo3/irre_localization.html
>>>>
>>>> I've upgraded the extension 'irre_tutorial' (available in TER) to
>>>> version 0.1.9 which supports the new configuration properties and 
>>>> offers
>>>> the possibility to test localization on several IRRE cases.
>>>>
>>>> References:
>>>> http://bugs.typo3.org/view.php?id=6087
>>>>
>> http://lists.netfielders.de/pipermail/typo3-project-irre/2008-January/000262.html 
>>
>>>>
>> news://news.netfielders.de/mailman.1.1200922393.17504.typo3-project-irre@lists.netfielders.de 
>>
>>>>
>>>> Sponsoring:
>>>> This feature is partly sponsored by the fotobuch.de AG -
>>>> http://www.fotobuch.de/ - thank you very much!
>>>>
>>>> Branch: Trunk
>>>>
>>>>
>>>> olly


-- 
Ingmar Schlecht
TYPO3 Association Active Member