Issue Bug New Quiet

#111083Configuration folder missing from default package resources or wrongly documented

Lina Wolf 10/15/26, 15:21 updated 10/15/26, 15:21

Description

Problem

The default resource definitions of an extension and the documentation of #109409 do not match.

typo3/sysext/core/Configuration/DefaultPackageResources.php defines only Resources/Private and, if it exists, Resources/Public. The Feature changelog “Feature-109409-Allow-configuration-of-public-resources.rst” describes the same defaults.

The Deprecation changelog “Deprecation-109409-Access-of-arbitrary-resources-in-extensions.rst” says that extension resources are limited by default to Configuration, Resources/Private, and Resources/Public. The runtime message in ResourceCollection::definitionForPath() says the same: “Resource identifiers outside ouf Resources/Private, Resources/Public or Configuration folder of extensions are deprecated.”

Impact

Configuration files of extensions are not affected: GeneralUtility::getFileAbsFileName(), the YAML loader, and the TypoScript and TSconfig includes resolve EXT: paths without the resource definitions.

The definitions are only checked by SystemResourceFactory::createResource() and createPublicResource(), for example in the PageRenderer, page.includeCSS and page.includeJS, the “asset” of a static route, f:resource, and SVG icons. A file below Configuration/ that is used there, for example “asset: EXT:my_sitepackage/Configuration/robots.txt”, triggers the deprecation. Once the on-the-fly fallback is removed, it throws SystemResourceDefinitionNotFoundException (1763381519).

Expected

Either add “new ResourceDefinition(‘Configuration’)” to DefaultPackageResources.php, or remove Configuration from the Deprecation changelog and the runtime message. In both cases fix the typo “ouf” in the message.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Configuration folder missing from default package resources or wrongly documented Resolves: #111083 Releases: main