Attention

TYPO3 v11 has reached end-of-life as of October 31th 2024 and is no longer being maintained. Use the version switcher on the top left of this page to select documentation for a supported version of TYPO3.

Need more time before upgrading? You can purchase Extended Long Term Support (ELTS) for TYPO3 v10 here: TYPO3 ELTS.

module

The backend module of an extension can be configured via TypoScript. The configuration is done in module.tx_<lowercaseextensionname>_<lowercasepluginname>. _<lowercasepluginname> can be ommited then the setting is used for all backend modules of that extension.

Even though we are in the backend context here we use TypoScript setup. The settings should be done globally and not changed on a per-page basis. Therefore they are usually done in the file EXT:my_extension/ext_typoscript_setup.typoscript.

Options for simple backend modules

In simple backend modules extension authors can decide how to use this namespace. By convention settings should go in the subsection settings.

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_myextension_somemodule {
    settings {
        enablesomething = 1
    }
}

Options for Extbase backend modules

Most configuration options that can be done for Extbase frontend plugins can also be done for Extbase backend modules:

view.templateRootPaths

view.templateRootPaths.[array]

Type: file path with stdWrap

Used to define several paths for templates, which are executed in reverse order (the paths are searched from bottom to top). The first folder where the desired layout is found is immediately used. If the array keys are numeric, they are first sorted and then executed in reverse order.

Example: Set the template root paths

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_somebackend_module {
    view {
        templateRootPaths {
            100 = EXT:my_extension/Resources/Private/Templates/Backend
        }
    }
}

view.partialRootPaths

view.partialRootPaths.[array]

Type: file path with stdWrap

Used to define several paths for partials, which will be executed in reverse order. The first folder where the desired partial is found, is used. The keys of the array define the order.

Example: Set the partial root paths

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_somebackend_module {
    view {
        partialRootPaths {
            100 = EXT:my_extension/Resources/Private/Partials/Backend
        }
    }
}

features.skipDefaultArguments

features.skipDefaultArguments

| Data type: boolean |

If enabled, default controller and/or action is skipped when creating URIs through the URI Builder. If a link to the default controller or action is created, the parameters are omitted.

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_somebackend_module {
    features {
        features.skipDefaultArguments = 1
    }
}

settings

settings

Type: array<string, mixed>

Here resides all of the settings. These settings are available in the controller of the backend module as the array variable $this->settings.

Example: Limit pagination in the backend

Show 25 news records in the backend module of the news extension:

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_news {
   settings.list.paginate.itemsPerPage = 25
}

Example: Register YAML file

Register your TYPO3 Form configuration for the backend via TypoScript.

EXT:my_extension/ext_typoscript_setup.typoscript

module.tx_form {
    settings {
        yamlConfigurations {
            # Use the current timestamp as key to avoid accidental overwriting
            1712163960 = EXT:my_extension/Configuration/Form/CustomFormSetup.yaml
        }
    }
}