---
title: "Deprecation: #100637 - Third argument ContentObjectRenderer->start()"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-100637-1681737971"
source: "Changelog/12.4/Deprecation-100637-ThirdArgumentContentObjectRenderer-start.rst"
typo3-version: "12.4"
typo3-major: 12
type: "deprecation"
issue: 100637
forge: "https://forge.typo3.org/issues/100637"
tags: ["Frontend", "PHP-API", "NotScanned", "ext:frontend"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Deprecation: #100637 - Third argument ContentObjectRenderer->start() {#deprecation-100637-1681737971}

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

## Description {#description}

When creating instances of the
`\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer`, the
third argument `$request` when calling `start()` should not be
handed over anymore. Instead, `setRequest()` should be used
after creating the object.

## Impact {#impact}

Handing over the third argument to `start()` has been marked as deprecated
in TYPO3 v12, it will be ignored with TYPO3 v13.

## Affected installations {#affected-installations}

Instances with casual extensions are probably not affected by this: Instances
of `ContentObjectRenderer` are usually set-up framework internally.

Using the third argument on `start()` triggers a deprecation level log
message. The extension scanner will *not* find usages, since the method
name `start()` is used in different context as well and would lead to
too many false positives.

## Migration {#migration}

Ensure the request is an instance of `\Psr\Http\Message\ServerRequestInterface`,
and call `setRequest()` after instantiation instead of calling
`start()` with three arguments.