[SOLVED] Problem displaying translated content elements

TYPO3 Questions Multilanguage
1

Hello everyone,

I have a Typo3 installation that is bilingual. It was set up via the site configuration in the Typo3 backend. The default language is German, the optional translation is in English.

On some pages I have the behavior, when I have selected the English language, that some content elements are displayed in English and some in German although an English translation is available. If I translate a page that does not yet have a translation, then only the German content is displayed.

I noticed this behavior after switching to Typo3v13. Does anyone have an idea why the Typo3 system behaves this way or a tip on how I could fix the error? Are there perhaps similar experiences?

Best regards
Mathias

2

I haven’t checked the changelogs on v13, but you could check your site config for the used “fallback” mode. See Localized content — Frontend Localization Guide 13.4 documentation in how to set it, maybe that helps?

3

Thanks for the hint, unfortunately I did not find any clue there. I noticed that the affected data records in the tt_content table all have the same settings. I was always of the opinion that Typo3 uses the database entries to determine the content elements for the respective language. Has this changed or is another table in the database responsible?

If the configuration was incorrect, then the content elements should not be delivered in different languages, should they?

4

Hi Mathias!

The issue you are describing could depend on missing or wrong language configurations in the Site configuration or a number of other issues. It will probably be easy to spot for an experienced TYPO3 integrator with access to your site — but difficult to debug through descriptions in a forum like this.

My recommendation would be that you seek help from a TYPO3 expert to debug your site and setup. An hour’s call should be sufficient for an initial assessment. Take a look at the listing for TYPO3 partners and TYPO3 Association members to find someone to contact.

5

Hello namesake ;-),

thank you very much for the tip about consulting an expert. However, I have once again looked into upgrading the Typo3 version and came across the problem by comparing the sequence step by step. An upgrade of the extension flux from version 10.0.10 to version 11.x caused the misbehavior. The bug has already been reported there several times and there is also a patch:

Perhaps it will help someone who also encounters this problem.

Best regards
Mathias

6

Hi @infastra!

Great to hear that you figured it out. This solution is great to have here on talk.typo3.org. Thank you for posting it!