Issue Bug New Orphaned

#104130Undesired translations of extbase relations are not sorted out like before

Hannes Bochmann 06/17/24, 14:33 updated 07/08/24, 17:55

Description

Following setup: There is a domain object that can not be translated (object A). This object has relations to some other object (B) that can be translated. All B objects have a field where the UID of object A is stored and all get the UID of object A even the translations. In the FE all related B objects are loaded no matter what language they are. Before TYPO3 12.4 all relations got sorted out that do not match the current FE language.

So my question is, is this intended behaviour, a bug or a problematic/faulty setup on my end? I could make object A translatable and than simply not use the UID of the default language object A for all relations but the UID of the translated object A. But than again object A needs no translations at least in TYPO3 10.4

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Undesired translations of extbase relations are not sorted out like before Resolves: #104130 Releases: main