Actions
Bug #61923
openLocalization of elements and their categories in the backend
Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
Categorization API
Target version:
-
Start date:
2014-09-27
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:
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?
Actions