---
title: "Breaking: #110319 - Removed unused internal Bootstrap methods"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-110319-1785315902"
source: "Changelog/15.0/Breaking-110319-RemovedUnusedInternalBootstrapMethods.rst"
modified: "2026-09-15T10:46:36+00:00"
---

# Breaking: #110319 - Removed unused internal Bootstrap methods

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

## Description

The following methods of `\TYPO3\CMS\Core\Core\Bootstrap` have been
removed:

-   `Bootstrap::baseSetup()`
-   `Bootstrap::createConfigurationManager()`
-   `Bootstrap::populateLocalConfiguration()`

All three were marked `@internal` and are not used by TYPO3 Core
anymore. `Bootstrap::baseSetup()` only registered the class loading
information in non-Composer mode, which `Bootstrap::init()` does
itself. The two configuration related methods have been inlined into
`Bootstrap::init()`, as they consisted of a single statement each.

## Impact

Calling one of the removed methods results in a fatal PHP error
(`Call to undefined method`).

## Affected installations

TYPO3 installations with third-party extensions or custom entry point
scripts that call `Bootstrap::baseSetup()` or
`Bootstrap::createConfigurationManager()` directly - a pattern
sometimes used in custom, non-Composer bootstrapping scripts.
`Bootstrap::populateLocalConfiguration()` was already
`protected` and could not be called from the outside.

The extension scanner reports possible usages.

## Migration

Remove calls to `Bootstrap::baseSetup()`,
`Bootstrap::init()` performs the equivalent setup internally.

Replace `Bootstrap::createConfigurationManager()` with a direct
instantiation:

```php
$configurationManager = new \TYPO3\CMS\Core\Configuration\ConfigurationManager();
```