Hi!

Franz Koch wrote:
> Thanks for your help, but I don't. I want the same (bound) content
> structure for all languages, but I don't want FCEs to be localized
> inline. All I want is to have the same possibility to use 'physical'
> language overlay records for FCEs as it's possible with regular content.
> I know that the FCE-fields can't be merged then, which is ok for me.
> And it's working when I use list-module or regular page module. But TVs
> page module is simply not providing the nice translation flag below the
> element for FCEs where 'langDisable' is set to 1 - which means for me
> that not only the flexform should get translated, but the whole CE. So
> the language flag should also appear here.
>
> See [1] for a example. The regular text CE can be translated by clicking
> on the british flag - the FCE not - but it should, because it's set to
> '<langDisable>1</langDisable>'. See what i mean? It's ok when the flag
> is missing for FCEs where inline-translation is enabled - but it should
> be there where it is disabled and the FCE's language is not set to 'all
> languages'.
>
> [1] http://hosting.elements-net.de/temp/...on-problem.png

Truly speaking I do not remember that particular part I seem to remember that setting langDisable=1 disable any way to localize FCE. And if you set it to 1, the value of langChildren is ignored.

What happens if you set langDisable to 0 and play with langChildren?

--
Dmitry Dulepov
TYPO3 Core team
More about TYPO3: http://typo3bloke.net/
Subscribe: http://typo3bloke.net/rss.xml
Latest article: http://typo3bloke.net/post-details/s...ivity_session/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila