[TYPO3-english] Multilanguage works for TemplaVoila FCEs but not for classical css_styled_content elements [SOLVED]

[Johannes K.]

Solved.

To enable TYPO3 looking for translated records of tt_content you need to add

#in Page TSconfig:
mod.web_layout.defLangBinding = 1

and
#Page Template
config.sys_language_overlay = 1

TemplaVoila does not need this, as it looks for translated entries 
inside it's FCEs. Thus we had the effect of displayed translated 
TemplaVoila content and classical css_styled_content elements remaining 
in default language (frontend).

Regards
Johannes

Am 14.09.2010 19:20, schrieb Johannes K.:
> Hello,
> I managed to enable a second language for my TemplaVoila FCEs. The FCEs
> have now in Backend every field double for the languages, ok. Switching
> language via menu in frontend shows the other language entries (thanks
> to the Typoscript Setup respecting the L= parameter). Fine.
>
> I also use some normal content elements (HTML, "only images", etc).
> Here the creation of a second language version is different: I have to
> switch from "default" to e.g. "German [NEW]" in the top menu Language in
> backend. Then a new content element is shown in backend with all fields
> for this language (showing the original values as a hint for
> translation). Ok, translated and saved (and cleared caches).
>
> Unfortunately after switching the language via menu in frontend TYPO3
> still shows the "default" language (L=0) for these elements (and only
> toggles the content of the TV FCEs).
>
> --> Is there any bug/case that the
> styles.content.get.select.languageField = sys_language_uid
> of css_styled_content does not work any more with TemplaVoila installed ?
>
> Thanks for your help.
> Regards
> Johannes


-- 
TYPO3 v4.4.2, EXT: TemplaVoila v1.4.4, Framework for TemplaVoila 
v1.1.0, static Infotables v2.1.2