---
title: "Breaking: #82639 - Logging activated for authentication and Service classes"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-82639"
source: "Changelog/9.0/Breaking-82639-LoggingActivatedForAuthenticationAndServiceClasses.rst"
modified: "2026-09-15T10:46:36+00:00"
---

# Breaking: #82639 - Logging activated for authentication and Service classes

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

## Description

Due to the introduction of TYPO3's Logging API in several places, it is now common to use the logging
API without further options.

Therefore the following configuration options have been removed:

-   `$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/class.t3lib_userauth.php']['writeDevLog']`
-   `$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/class.t3lib_userauth.php']['writeDevLogBE']`
-   `$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['t3lib/class.t3lib_userauth.php']['writeDevLogFE']`
-   `$GLOBALS['TYPO3_CONF_VARS']['SYS']['enable_DLOG']`

The following public properties have no effect anymore and have been removed:

-   `AbstractUserAuthentication->writeDevLog`
-   `AbstractService->writeDevLog`

## Impact

Setting any of the options does not have any effect anymore on logging.

## Affected Installations

Installations running with `EXT:devlog` or further extensions setting any of the options above.

## Migration

Instead of using the mentioned options, TYPO3's Logging API can be configured as stated in the
official documentation to write the logging messages to various places.