---
title: "Breaking: #83256 - Removed lockFilePath functionality"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-83256"
source: "Changelog/9.0/Breaking-83256-RemovedLockFilePathFunctionality.rst"
typo3-version: "9.0"
typo3-major: 9
type: "breaking"
issue: 83256
forge: "https://forge.typo3.org/issues/83256"
tags: ["Frontend", "TypoScript", "PartiallyScanned"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Breaking: #83256 - Removed lockFilePath functionality {#breaking-83256}

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

## Description {#description}

The TypoScript option `config.lockFilePath` has been removed, which was possible to allow TypoScript
`stdWrap.filelist` to use a different base directory than fileadmin/ (which was the default).

However, `stdWrap.filelist` now checks for valid local FAL storages (File Abstraction Layer), which can
now be used if multiple storages are in use.

Thus, the following PHP property has been removed:

-   `TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->lockFilePath`

The following PHP method has been removed:

-   `TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->clean_directory()`

## Impact {#impact}

Setting `config.lockFilePath` has no effect anymore.

Accessing or setting `TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController->lockFilePath` will trigger
a PHP notice.

Calling `TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->clean_directory()` will trigger a PHP fatal error.

## Affected Installations {#affected-installations}

Any installation using the PHP method/property or having config.lockFilePath set to a specific non-FAL folder,
and using `stdWrap.filelist` functionality.

## Migration {#migration}

If the TypoScript option was set to a different folder than a FAL storage, ensure to set a local FAL storage
to this folder.