Bug #45212
closedNo localization of MM select fields
0%
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.
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.4 (Backend)
- Is Regression set to No
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Mathias Schreiber about 9 years ago
- Target version changed from 7 LTS to 8 LTS
Updated by Benni Mack over 7 years ago
- Target version changed from 8 LTS to next-patchlevel
Updated by Oliver Hader about 7 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
Updated by Riccardo De Contardi almost 7 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.