remind/extbase

REMIND - Extbase

v2.0.0 2025-02-27 15:40 UTC

Requires

• php: ^8.2
• remind/routing: ^1.0 | dev-develop
• typo3/cms-backend: ^12.4
• typo3/cms-core: ^12.4
• typo3/cms-frontend: ^12.4

Requires (Dev)

• dealerdirect/phpcodesniffer-composer-installer: ^1.0
• phpstan/extension-installer: ^1.4
• phpstan/phpstan: ^1.12
• remind/coding-standard: ^1.0
• remind/headless: ^4.0 | dev-develop
• saschaegerer/phpstan-typo3: ^1.10
• slevomat/coding-standard: ^8.15
• squizlabs/php_codesniffer: ^3.11

Suggests

• remind/headless: Using Remind\Extbase\Service\JsonService requires remind/headless

GPL-3.0-or-later

• REMIND GmbH
• David Mellen

• cms
• typo3
• extbase
• REMIND

README

This extension provides basic functionality that can be used in other extbase extensions, mainly configurations and utilities/services for Plugins that allow consistent list, filter and detail views.

Plugins

Plugins can have on of three types: Detail, FilterableList or SelectionList. To configure a plugin using one of these types first register a plugin the usual way using TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin and then use the returned plugin signature along with the desired type and the table name to call Remind\Extbase\Utility\PluginUtility::addTcaType. These calls should happen in tt_content.php.

$filterableListSignature = ExtensionUtility::registerPlugin(
    'Products',
    'FilterableList',
    'LLL:EXT:rmnd_products/Resources/Private/Language/locallang_tca.xlf:filterableList',
    'productsfilterablelist',
    'Products'
);

PluginUtility::addTcaType($filterableListSignature, PluginType::FILTERABLE_LIST, 'tx_products_domain_model_product');

FilterValueMapper

Used to modify filter keys and check filter values. Filter query parameters use an array syntax like ?filter[name]=...&filter[title]=... and the FilterValueMapper allows to change the array key by using aspects. In addition, only values defined in pi_flexform field of tt_content with CType defined in config are allowed for values. parameters and aspects act the same as in ExtbaseQuery Route Enhancer config.

Example for ?filter[name]=...&filter[title]=...:

aspects:
  filter:
    type: FilterValueMapper
    tableName: tx_contacts_domain_model_contact
    cType: contacts_filterablelist
    parameters:
      keys:
        name: Name
        title: titleKey
    aspects:
      titleKey:
        type: LocaleModifier
        default: Title
        localeMap:
          -
            locale: 'de_DE.*'
            value: Titel

With these settings, the query parameters will look like this:

English: ?filter[Name]=...&filter[Title]=...

German: ?filter[Name]=...&filter[Titel]=...