Feature #105439
Updated by S P 6 days ago
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). field.
Back