Issue Bug Closed

#107515Page error handler subrequest: Desired storage "XXX" is not in the list of available storages

Christian Weiske 09/22/25, 09:09 updated 10/18/26, 13:08

Description

When a 404 page shall be rendered, rendering the error page fails with the following error:

> ½ #1314085990 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
> Desired storage “AusDriverAmazonS3” is not in the list of available storages.

This is because the PageContentErrorHandler stashes the environment, and with it the storage drivers. When the error page needs an image file from a non-local storage, it fails.
The problem is that the other drivers do not get loaded in the error subrequest.

Happens on TYPO3 v12.4.37.

Stack trace

(1/2) #1314085990 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
Desired storage "AusDriverAmazonS3" is not in the list of available storages.

[...]

(2/2) #1314085990 InvalidArgumentException
Desired storage "AusDriverAmazonS3" is not in the list of available storages.

in /var/www/typo3/vendor/typo3/cms-core/Classes/Resource/Driver/DriverRegistry.php line 124

at TYPO3\CMS\Core\Resource\Driver\DriverRegistry->getDriverClass() in /var/www/typo3/vendor/typo3/cms-core/Classes/Resource/StorageRepository.php line 495
at TYPO3\CMS\Core\Resource\StorageRepository->getDriverObject() in /var/www/typo3/vendor/typo3/cms-core/Classes/Resource/StorageRepository.php line 469
at TYPO3\CMS\Core\Resource\StorageRepository->createStorageObject() in /var/www/typo3/vendor/typo3/cms-core/Classes/Resource/StorageRepository.php line 369
at TYPO3\CMS\Core\Resource\StorageRepository->getStorageObject() in /var/www/typo3/vendor/typo3/cms-core/Classes/Resource/StorageRepository.php line 100
[...]
at TYPO3\CMS\Frontend\Http\Application->handle() in /var/www/typo3/vendor/typo3/cms-core/Classes/Error/PageErrorHandler/PageContentErrorHandler.php line 154
at TYPO3\CMS\Core\Error\PageErrorHandler\PageContentErrorHandler->sendSubRequest() in /var/www/typo3/vendor/typo3/cms-core/Classes/Error/PageErrorHandler/PageContentErrorHandler.php line 98
at TYPO3\CMS\Core\Error\PageErrorHandler\PageContentErrorHandler->TYPO3\CMS\Core\Error\PageErrorHandler\{closure}() in /var/www/typo3/vendor/typo3/cms-core/Classes/Error/PageErrorHandler/PageContentErrorHandler.php line 131
at TYPO3\CMS\Core\Error\PageErrorHandler\PageContentErrorHandler->stashEnvironment() in /var/www/typo3/vendor/typo3/cms-core/Classes/Error/PageErrorHandler/PageContentErrorHandler.php line 98
at TYPO3\CMS\Core\Error\PageErrorHandler\PageContentErrorHandler->handlePageError() in /var/www/typo3/vendor/typo3/cms-frontend/Classes/Controller/ErrorController.php line 85
at TYPO3\CMS\Frontend\Controller\ErrorController->pageNotFoundAction() in /var/www/typo3/vendor/typo3/cms-frontend/Classes/Middleware/PageResolver.php line 74
at TYPO3\CMS\Frontend\Middleware\PageResolver->process() in /var/www/typo3/vendor/typo3/cms-core/Classes/Http/MiddlewareDispatcher.php line 162
[...]

Reviews 1

History 7

  1. Christian Weiske commented <span data-processor="relativetime" data-value="2025-09-22T09:36:49+00:00" > 09/22/25, 09:36 </span>

    Note that this occurs when patch 85224 is applied (issue #103215)

  2. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-18T13:08:13+00:00" > 10/18/26, 13:08 </span>

    This only happens with patch 85224 (#103215) applied, which created a new DI container for the error sub request and thereby lost the registered storage drivers. That patch was abandoned and never merged.

    The current PageContentErrorHandler on main does not swap the container anymore. It resets the PageRenderer state and handles the sub request within the same container, so the storage drivers stay available. Not reproducible without the abandoned patch.

    If this is still valid for you in v14, please open a new issue and provide information how to reproduce it. Thanks!