Feature: #96515 - Aliases for Backend Routes and Backend Modules

See forge#96515


TYPO3 Backend Module and Routing functionality now allows to define a different route identifier (e.g. "record_edit") or module identifier (e.g. "web_layout" as the identifier for the Page Module) while also defining aliases for any previous identifier.

This is especially important when a module identifier should be changed to use a proper naming, reflecting the actual module, while keeping any links from within TYPO3's Backend extensions - e.g. third-party - to continue to work.

An upgrade wizard allows to continuously verify backend user and backend group permissions when a module identifier has been changed, as long as the previous identifier is added as an alias to the module configuration.


The new array key aliases in module and route configurations can be used to provide support for different names, which ultimately allows to rename route and module identifiers, since the old identifier can still be used to reference them.

Example for a new module identifier within Configuration/Backend/Modules.php:

return [
    'workspaces_admin' => [
        'parent' => 'web',
        // choose the previous name or an alternative name
        'aliases' => ['web_WorkspacesWorkspaces'],

Example for a route alias identifier within Configuration/Backend/Routes.php:

return [
    'file_editcontent' => [
        'path' => '/file/editcontent',
        'aliases' => ['file_edit'],