#89659Translating a record creates superfluous wrong mm relations
Description
Most easily reproduced with sys_category and sys_category_record_mm, but this generally is true for all tables that have MM relation tables.
- Have a
sys_categoryentry in L=0 - Have a record (tx_news or so) in L=0 or L=-1 using this category
sys_category_record_mmhas one entry for this relation -> still OK- translate the category to L=1
sys_category_record_mmhas now the original entry (L=0category -> L=0 record) and a false one connecting the L=0 record with L=1 category, the false one has a higher sorting and thus gets prioritized in FE
I tried several combinations of TCA settings (l10n_mode, dontRemapTablesOnCopy, localizeReferencesAtParentLocalization) which did not change anything.
I could not find the root cause for this behaviour.
This does not inherently break the FE rendering or categorization, but most likely lead to the situation that wrong translation labels are echoed into the FE.
It seems that this behaviour was recently introduced (one of the latest 9.5.x releases), because we have several big multi-language v9 setups that were working fine and recently we got customer feedback about this.
Reviews 3
Related issues 4
- Bug #62727Allow MM reference translation on non inline fields for bidirectional MM relations
- Bug #77902Translating category causes creation of non-necessary relations
- Bug #89620Creating MM relations in a group field with a translatable table causes translated records to show up twice
- Bug #91842Entries in sys_category_record_mm are created also for translated categories