---
title: "Feature: #93789 - Access the page context of backend requests"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-93789-1794239825"
source: "Changelog/15.0/Feature-93789-AccessThePageContextOfBackendRequests.rst"
typo3-version: "15.0"
typo3-major: 15
type: "feature"
issue: 93789
forge: "https://forge.typo3.org/issues/93789"
tags: ["Backend", "PHP-API", "ext:backend"]
rendered: "2026-11-14T17:17:53+00:00"
---

# Feature: #93789 - Access the page context of backend requests {#feature-93789-1794239825}

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

## Description {#description}

Backend modules and routes working with a page can now rely on the
request attribute `pageContext`, which carries a
`\TYPO3\CMS\Backend\Context\PageContext` object. Before, every
extension had to find out on its own which page a backend request is
about.

The attribute is added to the request of

-   every backend module using the page tree navigation component
    (`@typo3/backend/tree/page-tree-element`), either directly or
    inherited from its parent module, for example most of the modules
    below **Content**, and
-   every backend route with the option `requestPageContext` set to
    `true`, for example the record editing form.

The page is determined from the `id` argument of the request. Without
it, the page is taken from an `edit` statement (the page of the edited
record, or the target of a new record) or from a `cmd` statement (the
page of a deleted record, or the target of a copy or move command).
When no page can be determined, the context is created for page `0`.
The attribute is not set when no backend user is logged in, or when
the context cannot be created, so check it before using it.

The `PageContext` object provides

-   `pageId`: the requested page ID, even if the user has no access,
-   `pageRecord`: the page record, or `null` if the user has no access,
-   `site`: the site of the page,
-   `pageAncestry`: the `\TYPO3\CMS\Core\Domain\PageAncestry` of
    the page in the workspace of the user, or `null` if the user has no
    access,
-   `pageTsConfig`: the page TSconfig of the page,
-   `pagePermissions`: the permissions of the user on the page,
-   `selectedLanguageIds` and `languageInformation`: the languages
    selected in the module and the translations of the page, as
    `\TYPO3\CMS\Backend\Domain\Model\Language\PageLanguageInformation`,

as well as the methods `isAccessible()`,
`getPrimaryLanguageId()`, `hasMultipleLanguagesSelected()`,
`isLanguageSelected()`, `isDefaultLanguageSelected()`,
`getPageTitle()` and `getModuleTsConfig()`.

`PageContext`, `PageLanguageInformation`,
`LanguageItem` and `LanguageStatus` are now public API. Their
constructors remain internal: the objects are created by TYPO3 Core.

### Example {#example}

**EXT:my_extension/Classes/Controller/MyModuleController.php**

```php
use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Backend\Context\PageContext;

public function handleRequest(ServerRequestInterface $request): ResponseInterface
{
    $pageContext = $request->getAttribute('pageContext');
    if (!$pageContext instanceof PageContext) {
        throw new \RuntimeException('Page context not available', 1794239826);
    }
    if (!$pageContext->isAccessible()) {
        // Render a "no access" view
    }
    $pageId = $pageContext->pageId;
    $moduleTsConfig = $pageContext->getModuleTsConfig('my_module');
    // ...
}
```

A route that is not part of a module with the page tree requests the
page context with an option:

**EXT:my_extension/Configuration/Backend/Routes.php**

```php
return [
    'my_record_action' => [
        'path' => '/my-extension/record-action',
        'target' => \MyVendor\MyExtension\Controller\RecordActionController::class . '::handleRequest',
        'options' => [
            'requestPageContext' => true,
        ],
    ],
];
```

## Impact {#impact}

Extensions can read the current page, its site, its rootline, its page
TSconfig and the permissions of the user from the `pageContext`
request attribute, instead of evaluating the `id` argument and
fetching this information themselves.
