Project

General

Profile

Actions

Bug #45212

closed

No localization of MM select fields

Added by dtele Programmierer over 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2013-02-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Using the TCA field type "select" with an MM table prevents values to be properly mapped upon localization of the whole record.

This works fine for non-MM relations via foreign_field and even with IRRE. However, the processing in t3lib_TCEmain::copyRecord_procBasedOnFieldType simply transfers the original values to the localized copy.

If you use something like <foreign_table>.sys_language_uid IN (-1, 0) in your foreign_table_where, you at least see the original values afterwards. But the preferred display would be achieved via <foreign_table>.sys_language_uid = ###REC_FIELD_sys_language_uid###. Only this way foreign records with the same language as the local record are displayed.

There should be extra processing which takes into account possible translations of foreign records referred in such a field.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #51651: Translated record shows title of relation in default languageClosed2013-09-02

Actions
Related to TYPO3 Core - Bug #70522: processSelectFieldValue needs to happen before any processForeignTableClause is calledClosed2015-10-09

Actions
Actions #1

Updated by Mathias Schreiber over 9 years ago

  • Target version set to 7.4 (Backend)
  • Is Regression set to No
Actions #2

Updated by Susanne Moog almost 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #3

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #4

Updated by Mathias Schreiber over 8 years ago

  • Target version changed from 7 LTS to 8 LTS
Actions #5

Updated by Benni Mack about 7 years ago

  • Target version changed from 8 LTS to next-patchlevel
Actions #6

Updated by Oliver Hader over 6 years ago

  • Status changed from New to Needs Feedback

Does that still happen? If yes, please provide the relevant TCA field configurations of both parent and child entities. Thanks

Actions #7

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Needs Feedback to Closed
  • Target version deleted (next-patchlevel)

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF