---
title: "Feature: #97096 - Non-namespaced arguments in Extbase backend modules"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-97096"
source: "Changelog/12.0/Feature-97096-Non-namespacedArgumentsInExtbaseBackendModules.rst"
typo3-version: "12.0"
typo3-major: 12
type: "feature"
issue: 97096
forge: "https://forge.typo3.org/issues/97096"
tags: ["Backend", "PHP-API", "ext:extbase"]
rendered: "2026-09-23T19:53:57+00:00"
---

# Feature: #97096 - Non-namespaced arguments in Extbase backend modules {#feature-97096}

See [forge#97096](https://forge.typo3.org/issues/97096)

## Description {#description}

Extbase plugins and backend modules traditionally use the plugin / module
namespace to prefix their GET parameters and form data. In the frontend context,
this makes sense, as multiple plugins may reside on a page. In the backend,
however, an Extbase module is responsible for rendering a complete view.
Therefore, the namespacing of arguments has been disabled, making URLs easier
to read, more in line with non-Extbase modules and allowing Extbase modules
to directly access outside information like the `id` parameter handed over
by the page tree for example.

To allow Extbase modules to configure this behaviour, the Extbase feature
flag `enableNamespacedArgumentsForBackend` can be set in the module
configuration, turning the namespacing off or on.

## Impact {#impact}

Extbase will by default build and react to backend module links without paying
attention to the namespace of the parameters.

A link may look like this:

`https://example.org/typo3/module/web/BeuserTxBeuser?action=groups&controller=BackendUser`

If a module explicitly wants to keep using the namespaced version of the arguments,
the feature flag can be set:

**EXT:my_extension/ext_typoscript_setup.typoscript**

```typoscript
module.tx_myextension_somemodule {
    features {
        enableNamespacedArgumentsForBackend = 1
    }
}
```