---
title: "Deprecation: #107537 - GeneralUtility::createVersionNumberedFilename"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-107537-1760337101"
source: "Changelog/14.0/Deprecation-107537-CreateVersionNumberedFileName.rst"
typo3-version: "14.0"
typo3-major: 14
type: "deprecation"
issue: 107537
forge: "https://forge.typo3.org/issues/107537"
tags: ["PHP-API", "FullyScanned", "ext:core"]
rendered: "2026-09-23T15:30:34+00:00"
---

# Deprecation: #107537 - GeneralUtility::createVersionNumberedFilename {#deprecation-107537-1760337101}

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

## Description {#description}

`GeneralUtility::createVersionNumberedFilename` adds cache busting to a
file URL, when called in a certain and correct order with other legacy API
methods to create URLs from system resources.

This class and its functionality is superseded by the **System Resource API**.

## Impact {#impact}

Calling this method will trigger a PHP deprecation warning. The method will
continue to work as is, until it is removed in TYPO3 v15.0.

## Affected installations {#affected-installations}

TYPO3 installations with custom extensions or code that directly call this
deprecated method:

-   `GeneralUtility::createVersionNumberedFilename`

## Migration {#migration}

Use the **System Resource API** instead.

Before:

**MyClass**

```php
use TYPO3\CMS\Core\Utility\GeneralUtility;
use TYPO3\CMS\Core\Utility\PathUtility;

public function renderUrl(string $file): string
{
    $file = GeneralUtility::getFileAbsFileName($file);
    $partialUrl = GeneralUtility::createVersionNumberedFilename($file);
    return PathUtility::getAbsoluteWebPath($partialUrl);
}
```

After:

**MyClass**

```php
use TYPO3\CMS\Core\Http\ServerRequestInterface;
use TYPO3\CMS\Core\Resource\SystemResourceFactory;
use TYPO3\CMS\Core\Resource\SystemResourcePublisherInterface;
use TYPO3\CMS\Core\Resource\UriGenerationOptions;

public function __construct(
    private readonly SystemResourceFactory $systemResourceFactory,
    private readonly SystemResourcePublisherInterface $resourcePublisher,
) {}

public function renderUrl(
    string $resourceIdentifier,
    ServerRequestInterface $request
): string {
    $resource = $this->systemResourceFactory->createPublicResource(
        $resourceIdentifier
    );
    return (string)$this->resourcePublisher->generateUri(
        $resource,
        $request,
        new UriGenerationOptions(absoluteUri: true),
    );
}
```

> [!NOTE]
> The code should always be refactored to receive a request, which must then be passed to the API.
> If that is not possible due to restrictions in TYPO3 legacy API (e.g. Events or Hooks not passing the
> request, but an URL must be generated in the listener), null can be passed.
> Passing null instructs the API to check for `$GLOBALS['TYPO3_REQUEST']` and use it (if it exists).
> Be aware, though, that this global variable will deprecated and removed eventually.
>
> On CLI, `$GLOBALS['TYPO3_REQUEST']` is never available, neither is there a request.
> In that case, passing `null` to the API has the consequence that no absolute URLs (containing host
> and scheme) can be created. If you need absolute URLs based on a certain site on CLI,
> a request must be constructed accordingly and passed to the API.
> For more information about this and how to get/construct/mock the request object,
> see [TYPO3 request object](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/RequestLifeCycle/Typo3Request.html#typo3-request).