TYPO3 Core

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.

@R3H3 do I understand your case correctly, that locallang labels are not translated for you?
Then @David comments sounds like a different issue.

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.

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