#87946Wrong translation on multilanguage page in plugins
Description
Scenario:
Multidomain/Multilanguage installation:
+ Site A [de, fr, it]
+ Site B [fr]
Sylanguages:
- de: 0
- fr: 1
- it: 2
Sites are setup with site module.
On Site A, German is setup as default language.
On Site B, French is setup as default language.
Any Extbase plugin on Site B displays translated labels in German. Labels are translated with fluid viewhelper.
The problem is, that on Site B, the property “typo3Language” is “de” on the object SiteLanguage.
The Extbase LocalizationUtility is using this property, better would be twoLetterIsoCode.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 6
-
David Bruchmann commented <span data-processor="relativetime" data-value="2019-07-12T15:58:53+00:00" > 07/12/19, 15:58 </span>
-
Tymoteusz Motylewski commented <span data-processor="relativetime" data-value="2019-07-15T10:49:27+00:00" > 07/15/19, 10:49 </span>
R3H3 do I understand your case correctly, that locallang labels are not translated for you?David comments sounds like a different issue.
Then -
David Bruchmann commented <span data-processor="relativetime" data-value="2019-07-16T15:29:57+00:00" > 07/16/19, 15:29 </span>
Yeah @Tymoteusz ,sorry, my issue might be different.
By usage of a hook of the extension sysext/frontend (hook: getRecordOverlay_preProcess) it might be possible to determine the language for the labels correct, but it might depend on the extension. -
Jonas Schwabe commented <span data-processor="relativetime" data-value="2019-07-16T15:50:02+00:00" > 07/16/19, 15:50 </span>
David Bruchmann wrote:
> Yeah @Tymoteusz ,sorry, my issue might be different.
> By usage of a hook of the extension sysext/frontend (hook: getRecordOverlay_preProcess) it might be possible to determine the language for the labels correct, but it might depend on the extension.This is probably what you are referring to (I’m dealing with the same issue right now): #88784
-
Benni Mack commented and changed status
NewNeeds Feedback assigned to Benni Mack <span data-processor="relativetime" data-value="2024-01-24T09:33:02+00:00" > 01/24/24, 09:33 </span>Hey, we’ve made huge progress on this topic in the past TYPO3 versions – both with locale, labels (v12), and Extbase translation handling (v11+v12). Can you recheck with TYPO3 v12?
-
Benni Mack commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2024-12-10T15:14:38+00:00" > 12/10/24, 15:14 </span>Hey remo,
I’m closing this issue due to lack of feedback
The point is that extbase is doing some (messy) stuff concerning translations but it shouldn’t at all.
Usually records are still passed to the core and overlayed there – there it fails because extbase is messing up already before:
- Instead of letting the core doing it’s work, extbase is replacing records already by the (somehow determined) translation.
- Then the records get the wrong sys_language_uid (0) to pass the core functions without correct handling.
- core-handling of translations is not always correct too, but extbase shouldn’t care about it.
This is absolutely worst scenario, but it’s done like that and requires usage of at least one hook with further queries to fix extbase’s mess.