#98323auto creation of table isn't done if options never fit exact needs
Description
Having a configuration like this:
'related_posts' => [
'exclude' => true,
'label' => 'LLL:EXT:blog_example/Resources/Private/Language/locallang_db.xlf:tx_blogexample_domain_model_post.related',
'config' => [
'type' => 'select',
'renderType' => 'selectMultipleSideBySide',
'size' => 10,
'autoSizeMax' => 30,
'multiple' => 0,
'foreign_table' => 'tx_blogexample_domain_model_post',
'foreign_table_where' => 'AND ###THIS_UID### != tx_blogexample_domain_model_post.uid',
'MM' => 'tx_blogexample_post_post_mm',
'MM_opposite_field' => 'related_posts',
],
],
the table isn’t created.
The culprit here is the option ‘MM_opposite_field’, removing it, it works like expected.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 2
-
Benni Mack changed target version 10/04/22, 19:42
-
Christian Kuhn commented and changed status
NewRejected 10/11/22, 17:58
Hey.
That’s intended: MM table auto generation is always only created when looking at it from the “local” / “left” TCA table. With MM_opposite_field you specify you’re on the “foreign” / “right” side. That’s basically because there can be more than one “foreign” tables, so the DefaultTcaSchema always looks at MM from the “local” side only, to not mix up things.