Project

General

Profile

Actions

Bug #104130

open

Undesired translations of extbase relations are not sorted out like before

Added by Hannes Bochmann about 1 month ago. Updated 9 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Extbase + l10n
Target version:
-
Start date:
2024-06-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

Actions #1

Updated by Tymoteusz Motylewski 9 days ago

  • Assignee deleted (Tymoteusz Motylewski)
Actions

Also available in: Atom PDF