---
title: "Breaking: #110218 - Class LogRecord declared final"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-110218-1784306183"
source: "Changelog/15.0/Breaking-110218-LogRecordDeclaredFinal.rst"
typo3-version: "15.0"
typo3-major: 15
type: "breaking"
issue: 110218
forge: "https://forge.typo3.org/issues/110218"
tags: ["PHP-API", "NotScanned", "ext:core"]
rendered: "2026-10-07T18:53:34+00:00"
---

# Breaking: #110218 - Class LogRecord declared final {#breaking-110218-1784306183}

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

## Description {#description}

The PHP class `\TYPO3\CMS\Core\Log\LogRecord` — the value object passed
to log writers and processors — has been declared `final` and is now
instantiated directly via `new` within
`\TYPO3\CMS\Core\Log\Logger`, instead of using
`\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance()`.

A log record is a plain data transfer object created for every single log
entry. Routing its creation through `makeInstance()` allowed the class
to be overridden via XCLASS, but caused an unnecessary container lookup in
one of the most frequently executed code paths of the logging API.

In addition, the class now declares `strict_types` and uses native
type declarations for all method signatures instead of loose PHPDoc
annotations.

## Impact {#impact}

Extending or XCLASSing `\TYPO3\CMS\Core\Log\LogRecord` is not possible anymore. Extension
classes will raise a fatal PHP error, XCLASS configurations for this class
are silently ignored.

Calling a method of `\TYPO3\CMS\Core\Log\LogRecord` with a wrong argument type — for
example a non-float value for `setCreated()` — will raise a PHP
`\TypeError`, depending on the `strict_types` mode of the
calling code.

Creating, reading and modifying log records — for example in custom
implementations of
`\TYPO3\CMS\Core\Log\Processor\ProcessorInterface` or
`\TYPO3\CMS\Core\Log\Writer\WriterInterface` — continues to work as
before.

## Affected installations {#affected-installations}

TYPO3 installations with third-party extensions that extend or XCLASS the
class `\TYPO3\CMS\Core\Log\LogRecord`, which is very unlikely.

## Migration {#migration}

To enrich or modify log records, implement a custom log processor
(`\TYPO3\CMS\Core\Log\Processor\ProcessorInterface`), which may return a modified or newly created
`\TYPO3\CMS\Core\Log\LogRecord` instance. Custom output handling belongs in a log writer
(`\TYPO3\CMS\Core\Log\Writer\WriterInterface`).