---
title: "Breaking: #82368 - Signal 'afterExtensionConfigurationWrite' removed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-82368"
source: "Changelog/9.0/Breaking-82368-SignalAfterExtensionConfigurationWriteRemoved.rst"
typo3-version: "9.0"
typo3-major: 9
type: "breaking"
issue: 82368
forge: "https://forge.typo3.org/issues/82368"
tags: ["Backend", "LocalConfiguration", "PHP-API", "NotScanned", "ext:extensionmanager"]
rendered: "2026-09-18T10:44:28+00:00"
---

# Breaking: #82368 - Signal 'afterExtensionConfigurationWrite' removed {#breaking-82368}

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

## Description {#description}

The extension manager no longer emits signal `afterExtensionConfigurationWrite`.
The code has been moved to the install tool which does not load signal / slot
information at this point.

## Impact {#impact}

Slots of this signal are no longer executed.

## Affected Installations {#affected-installations}

Extensions that use signal `afterExtensionConfigurationWrite`. This is a rather seldom
used signal, relevant mostly only for distributions.

## Migration {#migration}

In many cases it should be possible to use signal `afterExtensionInstall` of class
`\TYPO3\CMS\Extensionmanager\Utility\InstallUtility` instead which is fired after an extension
has been installed.