---
title: "Breaking: #97926 - Extbase QuerySettings methods removed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-97926-1657726187"
source: "Changelog/12.0/Breaking-97926-ExtbaseQuerySettingsMethodsRemoved.rst"
typo3-version: "12.0"
typo3-major: 12
type: "breaking"
issue: 97926
forge: "https://forge.typo3.org/issues/97926"
tags: ["PHP-API", "FullyScanned", "ext:extbase"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Breaking: #97926 - Extbase QuerySettings methods removed {#breaking-97926-1657726187}

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

## Description {#description}

Extbase's Persistence functionality is basing ORM queries on certain settings
usually fetched from `QuerySettingsInterface`, with a default
implementation `Typo3QuerySettings`.

The interface itself has changed so that it now requires two new methods:

`QuerySettingsInterface::getLanguageAspect(): LanguageAspect`
`QuerySettingsInterface::setLanguageAspect(LanguageAspect $aspect)`

The LanguageAspect covers both the overlay functionality and setting the
language ID.

For this reason, the following methods are removed from
`QuerySettingsInterface`:

-   `QuerySettingsInterface::getLanguageOverlayMode()`
-   `QuerySettingsInterface::setLanguageOverlayMode($languageOverlayMode)`
-   `QuerySettingsInterface::getLanguageUid()`
-   `QuerySettingsInterface::setLanguageUid($languageUid)`

All adaptions have been made to the default implementation in
`Typo3QuerySettings`, however the removed methods from the interface are kept
within the implementation to avoid fatal PHP errors.

## Impact {#impact}

Any custom implementation of `QuerySettingsInterface` needs to implement
the newly defined methods of the interface.

## Affected installations {#affected-installations}

TYPO3 installations with custom Extbase extensions dealing with QuerySettings
that are adjusted with the methods used above.

## Migration {#migration}

Switch the affected extensions via PHP to calling the newly added methods, as this is
how TYPO3 Core behaves the most reliable.