[TYPO3-l10nmgr] Better support for TemplaVoila

[Felix Nagel]

Am 24.06.2011 09:02, schrieb Andreas Kiessling:
> Hi Felix,
>
> i hope i got you right:
> you want to translate FCEs with separate content elements, so the
> translation is not done inline but fetched from a new row in the database?
>
> There's an undocumented setting which enables these FCEs to use with
> l10nmgr.
>
> Quoting from the Changelog:
> https://svn.typo3.org/TYPO3v4/Extensions/l10nmgr/trunk/ChangeLog
>
> 2008-02-15 Daniel Pötzinger
> * introduce new FCE translationMode:
> <langDatabaseOverlay>1</langDatabaseOverlay>
> * => therefore allow translation of flexforms also for overlay records
>
> Just put that right under the langDisable setting.
>
>
> You also might want to enable localizing your FCEs from the TV page module:
> http://bugs.typo3.org/view.php?id=16521
>
> Put this in your page ts:
> mod.web_txtemplavoilaM1.enableLocalizationLinkForFCEs = 1
>
>
> HTH,
> Andreas
>
Hey Andreas,

thanks so much for your post! It seems this solves my problem.

Just one question: Im not quit into the technique behind the FCE 
translation but when I did understand the "normal" TV way is to save the 
translation as XML which leads to problems when using l10nmgr.

With the proposed option the translations will be saved as new records 
like in normal templating mode (without TV). Afaik the langDisable 
already forces TV to add the translatiosn within a new tt_content entry. 
What exactly does langDatabaseOverlay when used with langDisable? I was 
not able to notice any differences in the DB.

So, are there any disadvanteges when adding langDatabaseOverlay to 
langDisable in a already partly translated installation?


The hint with the enableLocalizationLinkForFCEs is great! I already 
missed these links, THX!

Thanks for your help, really appreciated!

-- 
Regards
Felix Nagel