---
title: "Deprecation: #95009 - Passing TypoScript configuration as constructor argument to Exception handler"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-95009"
source: "Changelog/11.4/Deprecation-95009-PassingTypoScriptConfigurationAsConstructorArgumentToExceptionHandler.rst"
typo3-version: "11.4"
typo3-major: 11
type: "deprecation"
issue: 95009
forge: "https://forge.typo3.org/issues/95009"
tags: ["Frontend", "PHP-API", "NotScanned", "ext:frontend"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Deprecation: #95009 - Passing TypoScript configuration as constructor argument to Exception handler {#deprecation-95009}

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

## Description {#description}

With `config.contentObjectExceptionHandler` it's possible to
adjust the exception handler behavior of the frontend. It's even possible
to use an own exception handler class. Previously, the TypoScript configuration
was therefore passed to the exception handler via a constructor argument. This
has now been deprecated to allow the use of DI.

The configuration will now be passed using the new `setConfiguration()`
method. This method will be enforced by the `ExceptionHandlerInterface`
in TYPO3 v12.

## Impact {#impact}

Using a custom exception handler, while not implementing the `setConfiguration()`
method will trigger a deprecation log entry. The method will be enforced
in TYPO3 v12.

## Affected Installations {#affected-installations}

All installations defining a custom exception handler via the TypoScript
configuration `config.contentObjectExceptionHandler`, while
not implementing the `setConfiguration()` method.

## Migration {#migration}

Remove the `$configuration` argument from the constructor of any
custom exception handler class and implement the `setConfiguration()`
method instead.