Project

General

Profile

Actions

Bug #54250

closed

Extbase: MM_match_fields is not considered in MM-Selects

Added by Stefan Froemken over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
Start date:
2013-12-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

Hello Extbase-Team,

I have a category field in my extension:

'categories' => array(
    'exclude' => 1,
    'label' => 'LLL:EXT:jw_forms/Resources/Private/Language/locallang_db.xml:tx_jwforms_domain_model_form.categories',
    'config' => array(
        'type' => 'select',
        'foreign_table' => 'sys_category',
        'MM' => 'sys_category_record_mm',
        'MM_match_fields' => array(
            'tablenames' => 'tx_jwforms_domain_model_form',
        ),
        'MM_opposite_field' => 'items',
        'renderMode' => 'tree',
        'treeConfig' => array(
            'rootUid' => 0,
            'parentField' => 'parent',
            'appearance' => array(
                'showHeader' => TRUE,
                'expandAll' => FALSE,
            ),
        ),
        'minitems' => 0,
        'maxitems' => 5,
    ),
),

Then I build my query:

if ($settings['categories']) {
    $categories = t3lib_div::trimExplode(',', $settings['categories']);
    $constraintAnd[] = $query->in('categories.uid', $categories);
}

As you know the categories has to be differed by tablenames, but this querypart isn't there. This results in wrong records from db.

Stefan

Actions

Also available in: Atom PDF