Feature #105439
open
MM_match_fields not respected when auto-generating MM tables on relations without MM_opposite_field
0%
Description
I am not sure whether this is actually a bug, a missing feature or a documentation inconsistency (https://docs.typo3.org/m/typo3/reference-tca/13.4/en-us/ColumnsConfig/CommonProperties/Mm.html does not mention this at all, neither as a feature or a limitation).
Since v11 MM tables are autogenerated. The fields in MM_match_fields are not autogenerated, but have to be declared manually in ext_tables.sql. I expected them to be auto-generated, but they are not.
If this is intended behaviour the docs should have a note about this limitation.
EDIT: I noticed that it works when having MM_opposite_field alongside. But MM_match_fields do not neccessarily require an opposite field (it is totally valid architecture to have two, or more, local fields poitning to the same foreing table, using the same MM table without bidirectional usage).
Updated by
Updated by Nikita Hovratov 3 days ago
- Tracker changed from Bug to Feature
- TYPO3 Version deleted (
13)
This is true, they are not auto-generated. This needs some thought on how to handle properly. This is also interesting for the Content Blocks extension, as we do our own auto generation of those fields.