#24192tcatree delivers different tree with mm than without
Description
there are completly different results when using a configuration which should be only considered for saving relations.
I list some examples which only work after a workaround of #24191
1) using mm
———————————-
’config’ => array (
‘type’ => ‘select’,
‘internal_type’ => ‘db’,
‘size’ => 20,
‘minitems’ => 0,
‘maxitems’ => 999,
‘foreign_table’ => ‘pages’,
‘foreign_table_where’ => ‘ORDER BY pages.uid’,
‘MM’ => ‘tx_ktmbanner_usecase_pages_mm’,
‘renderMode’ => ‘tree’,
‘treeConfig’ => array(
// ‘rootUid’ => 214,
‘parentField’ => ‘pid’,
‘appearance’ => array(
‘expandAll’ => TRUE,
‘showHeader’ => TRUE,
‘maxLevels’ => 2,
)
),
),
———————————-
=> no records shown
2) hiding mm-relation
———————————-
’pages’ => array (
‘exclude’ => 0,
‘label’ => ‘LLL:EXT:banner/locallang_db.xml:tx_banner_domain_model_banner.pages’,
’config’ => array (
‘type’ => ‘select’,
‘internal_type’ => ‘db’,
‘size’ => 20,
‘minitems’ => 0,
‘maxitems’ => 999,
‘foreign_table’ => ‘pages’,
‘foreign_table_where’ => ‘ORDER BY pages.uid’,
// ‘MM’ => ‘tx_ktmbanner_usecase_pages_mm’,
‘renderMode’ => ‘tree’,
‘treeConfig’ => array(
// ‘rootUid’ => 214,
‘parentField’ => ‘pid’,
‘appearance’ => array(
‘expandAll’ => TRUE,
‘showHeader’ => TRUE,
‘maxLevels’ => 2,
)
),
),
———————————-
=> works fine
(issue imported from #M16554)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.