Feature: #99647 - Specific routes for backend modules

See forge#99647


With forge#96733 the new module registration API has been introduced. One of the main features is the explicit definition of the module routes. To further improve the registration, it is now possible to define specific routes for the modules, targeting any controller / action combination. Previously the target of a module usually targeted a controller action like handleRequest(), which then forwarded the request internally to a specific action, specified by e.g. a query argument. Such umbrella method can now be omitted by directly using the target action as target in the module configuration.

Additionally, this also makes any HTTP method check in the controller superfluous, since the allowed methods can now also be defined directly in the module configuration for each sub-route.


return [
    'my_module' => [
        'parent' => 'web',
        'path' => '/module/web/my-module',
        'routes' => [
            '_default' => [
                'target' => MyModuleController::class . '::overview',
            'edit' => [
                'path' => '/custom-path',
                'target' => MyModuleController::class . '::edit',
            'manage' => [
                'target' => AnotherController::class . '::manage',
                'methods' => ['POST'],

In case the path option is omitted for a sub-route, its identifier is automatically used as path, e.g. /manage.

All sub-routes are automatically registered in a \TYPO3\CMS\Core\Routing\RouteCollection. The full route identifier syntax is <module_identifier>.<sub_route>, for example my_module.edit. Using the \TYPO3\CMS\Backend\Routing\UriBuilder to create a link to such sub-route could therefore look like this:


Extbase modules

Also Extbase backend modules are enhanced and define now automatically explicit routes for each controller / action combination, as long as the enableNamespacedArgumentsForBackend feature toggle is turned off, which is the default. This means, the following module configuration

return [
    'web_ExtkeyExample' => [
        'parent' => 'web',
        'position' => ['after' => 'web_info'],
        'access' => 'admin',
        'workspaces' => 'live',
        'iconIdentifier' => 'module-example',
        'path' => '/module/web/ExtkeyExample',
        'labels' => 'LLL:EXT:beuser/Resources/Private/Language/locallang_mod.xlf',
        'extensionName' => 'Extkey',
        'controllerActions' => [
            MyModuleController::class => [

now leads to following URLs:

  • https://example.com/typo3/module/web/ExtkeyExample

  • https://example.com/typo3/module/web/ExtkeyExample/MyModuleController/list

  • https://example.com/typo3/module/web/ExtkeyExample/MyModuleController/detail

The route identifier of corresponding routes is registered with similar syntax as standard backend modules: <module_identifier>.<controller>_<action>. Above configuration will therefore register the following routes:

  • web_ExtkeyExample

  • web_ExtkeyExample.MyModuleController_list

  • web_ExtkeyExample.MyModuleController_detail


It is now possible to configure specific routes for a module, which all can target any controller / action combination.

As long as enableNamespacedArgumentsForBackend is turned off for Extbase backend modules, all controller / action combinations are explicitly registered as individual routes. This effectively means human-readable URLs, since the controller / action combinations are no longer defined via query parameters but are now part of the path.