---
title: "Deprecation: #84307 - Protected methods and properties in NewContentElementController"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-84307"
source: "Changelog/9.2/Deprecation-84307-ProtectedMethodsAndPropertiesInNewContentElementController.rst"
typo3-version: "9.2"
typo3-major: 9
type: "deprecation"
issue: 84307
forge: "https://forge.typo3.org/issues/84307"
tags: ["Backend", "PHP-API", "PartiallyScanned"]
rendered: "2026-09-24T15:27:11+00:00"
---

# Deprecation: #84307 - Protected methods and properties in NewContentElementController {#deprecation-84307}

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

## Description {#description}

This file is about third party usage of `\TYPO3\CMS\Backend\Controller\ContentElement\NewContentElementController`.

A series of class properties has been set to protected.
They will throw deprecation warnings if called public from outside:

-   \[not scanned\] `id`
-   `sys_language`
-   `R_URI`
-   `colPos`
-   `uid_pid`
-   \[not scanned\] `modTSconfig`
-   \[not scanned\] `doc`
-   \[not scanned\] `content`
-   `access`
-   \[not scanned\] `config`

All methods not used as entry points by `\TYPO3\CMS\Backend\Http\RouteDispatcher` will be
removed or set to protected in v10 and throw deprecation warnings if used from a third party:

-   \[not scanned\] `init()`
-   \[not scanned\] `main()`

## Impact {#impact}

Calling one of the above methods or accessing one of the above properties on an instance of
`NewContentElementController` will throw a deprecation warning in v9 and a PHP fatal in v10.

## Affected Installations {#affected-installations}

The extension scanner will find most usages, but may also find some false positives. The most
common property and method names like `$content` are not registered and will not be found
if an extension uses that on an instance of `NewContentElementController`.

In general all extensions that set properties or call methods except `mainAction()` or `wizardAction()` are affected.

## Migration {#migration}

In general, extensions should not instantiate and re-use controllers of the core. Existing
usages should be rewritten to be free of calls like these.