Bug #101720
closedsys_category_mm does not have a unique key
0%
Description
So the following happened: Upon an import someone :trademark: accidentally imported the data of the table sys_category_mm twice but did not notice as there was not key. The Form engine or whatever could not handle this and deleted all categories attached to a record on the next saving of said record. In the fronted you did not notice a problem except in those places where all categories should be listed, there they where listed twice. To me it sounds like a core bug that sys_category_mm has (at least in TYPO3 v11) no key?
The bug seems to happen somewhere in the category tree or form engine. The TCA used for the affected fields is for example:
'wco_sitepackage_xyz_categories_for_submenu' => [ 'label' => 'Kategorien im MenĂ¼ anzeigen', 'config'=> [ 'type' => 'category', ], ],
Updated by Christian Kuhn 12 months ago
- Related to Task #101425: TYPO3 and MariaDB Galera Cluster (PRIMARY KEY) added
Updated by Christian Kuhn 12 months ago
- Status changed from New to Needs Feedback
This has been changed in main & v12 with #101425: mm tables now either have a uid as primary key, or a combined primary key when there is no uid. Primary keys are always unique. This change needed various pre- and post-patches and had some impact, so we did not add it to v11.
Is this fine with you, Lina?
Updated by Christian Kuhn 12 months ago
- Status changed from Needs Feedback to Closed
Got "please close" from Lina.