Issue Bug Closed

#61923Localization of elements and their categories in the backend

Kurt Gusbeth 09/27/14, 22:01 updated 11/06/26, 11:02

Description

I am using makeCategorizable like this in my extension:

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::makeCategorizable(
    $_EXTKEY,
    'tx_ext_domain_model_content',
    $fieldName = 'categories',
    $options = array()
);

and:

CREATE TABLE tx_ext_domain_model_content (
    ...
    categories int(11) DEFAULT '0' NOT NULL,
    ...
);

The problem: the relations between sys_category and tx_ext_domain_model_content in sys_category_record_mm are not correct for translated elements when saving a translated element of the extension.
When I save a translated element (sys_language_uid=1), than Typo3 uses the UID of the original categories (sys_language_uid=0) for the relations in sys_category_record_mm.
Thats wrong. Typo3 should use the UID of the translated categories.
This happens only when saving a translated element.
Typo3 uses the tranalated UIDs of categories after the localization of categories or elements.
Conclusion: the main problem is that Typo3 shows only the original categories (sys_language_uid=0) even for translated elements and thats why Typo3 saves the wrong UID of the categories in sys_category_record_mm.
Is there any way to show the translated categories for translated elements?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 7

  1. Benni Mack commented and changed status Accepted Closed <span data-processor="relativetime" data-value="2026-11-06T11:02:17+00:00" > 11/06/26, 11:02 </span>

    On current main, translated records consistently relate to the default-language categories: the category tree only offers categories with sys_language_uid IN (-1, 0), and localizing a record no longer remaps MM relations to translated categories (see the CategoryManyToMany DataHandler scenarios). The frontend applies the overlay of the category. The inconsistency described here doesn’t exist any more, so I’m closing this issue. If you need translation-specific categories, please open a feature request.