TYPO3 Core

Consider the following Example:

Categories <-- m:m --> Products

TCA:

tx_heimspiel_domain_model_category.php

'products' => array(
    'config' => array(
        'type' => 'select',
        'foreign_table' => 'tx_heimspiel_domain_model_product',
        'MM' => 'tx_heimspiel_product_category_mm',
        'MM_opposite_field' => 'categories',
    )
)

tx_heimspiel_domain_model_product.php

'categories' => array(
    'config' => array(
        'type' => 'select',
        'foreign_table' => 'tx_heimspiel_domain_model_category',
        'MM' => 'tx_heimspiel_product_category_mm',
    )
),

You have a category C1 and a localized version C1Localized and a product P1 that is associated with C1 through the MM table.

If you now localize P1 to P1Localized the expected result is that P1Localized is associated with C1Localized through the MM table, but what happens is that P1Localized gets associated to C1 through the MM table.

I propose allowing localizeReferencesAtParentLocalization to be used in conjunction with MM tables, which would allow for the expected behavior.

Attached is a 1 line diff to make that happen.