---
title: "Deprecation: #82438 - Deprecation methods"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-82438"
source: "Changelog/9.0/Deprecation-82438-DeprecationMethods.rst"
modified: "2026-09-15T10:46:36+00:00"
---

# Deprecation: #82438 - Deprecation methods

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

## Description

The deprecation log related methods from GeneralUtility along with a
related configuration option have been deprecated:

-   `GeneralUtility::logDeprecatedFunction()`
-   `GeneralUtility::deprecationLog()`
-   `GeneralUtility::getDeprecationLogFileName()`
-   `GeneralUtility::logDeprecatedViewHelperAttribute()`
-   `$GLOBALS['TYPO3_CONF_VARS']['SYS']['enableDeprecationLog']` has no effect anymore

Deprecations now use PHP method `trigger_error('a message', E_USER_DEPRECATED)` and run
through the logging and exception stack of the TYPO3 core.  In development context deprecations
are turned into exceptions by default and ignored in production context.

## Impact

The file `typo3conf/deprecation_xy.log` is no longer filled by the core. However, if an
extension still uses methods like `GeneralUtility::logDeprecatedFunction()` it is
still filled with these messages, and throws an additional PHP E_USER_DEPRECATED message.

## Affected Installations

Installations with extensions that use one of the above methods.

## Migration

Extension authors should switch to `trigger_error('A useful message', E_USER_DEPRECATED);`