PHP freelancer, web developer, mobile web enthusiast

Problem:

• you have a Typo3 site with several languages
• you are using the media field in the page setup to show a header image or similar (under “Files:” in the page setup)
• you are using levelmedia in the typo3 template setup to put this media somewhere on the page
• the header image (media in general) is not shown in languages other than the default one

Solution:

• go to the install tool of your Typo3 site
• search for “pageOverlayFields” under “All Configuration”
• take out “media” in the list of fields under [FE][pageOverlayFields]

That’s it. Please keep in mind that ALL media now will be taken from the media field of the default language.

Thanks to just2b at TYPO3.net for mentioning the solution.

Have you come across a strange error message in your Typo3 Flexible Content Elements (FCE) saying that “langChildren = 0” and it is probably a configuration error? You will probaby have looked around where to set this configuration value…and you will probably not have found it. So here’s how you can fix it:

In TemplaVoila look for your FCE’s data structure (DS) and klick on the pen next to the title, not the title, then you should see the XML of this DS starting like this:





...



There you need to add the meta section and add the langDisable and langChildren properties. For container Elements you will most likely not require different language versions, so setting the values to 1 for both properties works well. The XML of your DS should now look like this:





1
1


...




This way translations are in the “separate” mode. However, for DS in multi-language sites a good way to go is the “Inheritance” mode. There you keep the page layout and structure across multiple pages, and content is inherited from the default language, so basically the translated version looks exactly the same as the one in the default language. The cool thing is that you can now translate selected content elements to other languages and keep others the way they are. So e.g. images can stay the same, but texts can now be translated.

You should definitely have a look at section “FlexForms” in the Frontend Localization Guide , also available as PDF for further reference! Hope this helps somebody.