Project

General

Profile

Actions

Bug #79934

closed

Localized one/many to many not mapped correctly

Added by Axel Helmert about 7 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
Extbase + l10n
Target version:
-
Start date:
2017-02-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
persistence mapping
Complexity:
medium
Is Regression:
Yes
Sprint Focus:

Description

We've experienced issues when defining a reference like a file reference with \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig() in TCA and translating the record in the TYPO3 list Module.
This is not limited to file references, it also affects any field defined with type inline and [behaviour][localizationMode] = 'select'.

Steps to reproduce:

  1. Define a domain model with a file reference.
  2. Create a page with multiple languages
  3. Create a record for your domain model in the TYPO3 list module
  4. Translate this record to another language
  5. In the translation record change the file reference to another file

Actual behavior:

In backend everything looks file the Default language of the record has file A and the translation record has file B.
In the frontend however, the record itself seems to be translated when switching languages, but always references file A.

Expected behavior:
The translated record should have a reference to file B in frontend.

I have implemented a fix and will push it to gerrit.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #82363: Make Extbase translation handling consistent with typoscriptClosedTymoteusz Motylewski2017-09-07

Actions
Is duplicate of TYPO3 Core - Bug #57272: Extbase doesn't handle FAL translations correctlyClosed2014-03-25

Actions
Actions

Also available in: Atom PDF