#109686TYPO3 14 - legacy installation - System resource API - Project path "public/typo3temp/assets/css/" is not allowed
Description
TYPO3 14 minimal installation (no third-party extension enabled/installed – no custom typoscript or so, only auto generated site-config.yaml) shows the ERROR at the frontend:
’Project path “public/typo3temp/assets/css/7015c8c4ac5ff815b57530b221005fc6.css” is not allowed. Define custom resources if required.’
TYPO3 14.3.0 – PHP 8.5 – symlink installation with ENV:
- TYPO3_PATH_APP = /httpdocs/myproject
- TYPO3_PATH_ROOT = /httpsdocs/myproject/public
- TYPO3_CONTEXT = Development
Since the “public/typo3temp” folder is allowed by default according to the documentation, I assume this is an error.
https://docs.typo3.org/c/typo3/cms-core/main/en-us//Changelog/14.0/Feature-107537-SystemResourceAPIForSystemFileAccessAndPublicUriGeneration.html#app-resource
Workaround:
add “public/typo3temp/assets” to $GLOBALS[‘TYPO3_CONF_VARS’][‘FE’][‘addAllowedPaths’].
Reviews 2
Files 2
History 1012
-
Helmut Hummel commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-04-22T12:10:33+00:00" > 04/22/26, 12:10 </span> -
Christian Hackl commented <span data-processor="relativetime" data-value="2026-04-22T13:10:27+00:00" > 04/22/26, 13:10 </span>
Hmm, if I’m reading this correctly, it’s supported since TYPO3 9; see:
https://docs.typo3.org/m/typo3/reference-coreapi/9.5/en-us/ApiOverview/Environment/Index.html#configuring-environment-pathsI can’t find anything to the contrary, or any indication that it was ever deprecated.
And we using it since then, without any problems.Even if it weren’t supported, I’d suggest that it be supported, since it definitely improves security—for example, by storing log files outside the DocRoot.
-
Christian Hackl commented <span data-processor="relativetime" data-value="2026-04-22T14:03:35+00:00" > 04/22/26, 14:03 </span>
For BE modules and CSS / JavaScript resources, the same error appears, e. g.:
Resolved resource “PKG:typo3/app:public/typo3conf/ext/hh_ext_filesize/Resources/Public/Css/backend/filesizes.css” is not a public resource. Given resource identifier: “PKG:typo3/app:public/typo3conf/ext/hh_ext_filesize/Resources/Public/Css/backend/filesizes.css”
Included via:
<f:be pagetitle="foo"><br> includeCssFiles="{0: '{f:uri.resource(path:\'Css/backend/filesizes.css\')}'}"<br> includeJsFiles="{0: '{f:uri.resource(path:\'JavaScript/backend/sortable.min.js\')}'}" /></f:be> -
Helmut Hummel changed Duplicated by #109685 <span data-processor="relativetime" data-value="2026-04-23T14:23:59+00:00" > 04/23/26, 14:23 </span>
-
Helmut Hummel changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-04-23T14:24:42+00:00" > 04/23/26, 14:24 </span> -
Helmut Hummel changed status
ClosedAccepted <span data-processor="relativetime" data-value="2026-04-23T14:57:44+00:00" > 04/23/26, 14:57 </span> -
Hannes Bochmann commented <span data-processor="relativetime" data-value="2026-09-08T13:35:16+00:00" > 09/08/26, 13:35 </span>
I ran into the same problem. This was due to the default JS TYPO3 adds when config.spamProtectEmailAddresses is set. By default TYPO3\CMS\Core\Page\DefaultJavaScriptAssetTrait writes the JS to typo3temp. Adding htdocs/typo3temp/assets to FE|addAllowedPaths was no workaround. I had to set config.removeDefaultJS = 0 so the JS is not written to typo3temp but used from EXT:frontend. But this is just a workaround obviously.
-
Gerrit Code Review pushed patch set 1 for main to change 97354 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-11-05T07:58:28+00:00" > 11/05/26, 07:58 </span> -
Oliver Bartsch commented <span data-processor="relativetime" data-value="2026-11-05T08:01:18+00:00" > 11/05/26, 08:01 </span>
Hey,
thanks for the report and the details. I think this actually is a bug. Since #109470, classic mode supports a public folder inside the project folder.
In classic mode the PackageManager created the virtual app package
typo3/appwith a hardcoded empty relative public path. So the default public resources_assets,uploadsandtypo3temp/assetswere defined relative to the project folder, not topublic/. Files the core writes topublic/typo3temp/assets/(inline CSS/JS, the default JavaScript forconfig.spamProtectEmailAddressesetc.) are resolved asPKG:typo3/app:public/typo3temp/assets/.... They matched none of these definitions, which led to an exception.I pushed a patch that passes
Environment::getRelativePublicPath()instead, as Composer mode already does. With a public sub-folder, the defaults now becomepublic/_assets,public/uploadsandpublic/typo3temp/assets, and they are recognized as already public. Installations where the project folder is the public folder are not affected, because the relative public path is still empty there. Custom definitions inconfig/system/resources.phpnow get the correct relative public path, too.Cheers, Oli
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 97365 <span data-processor="relativetime" data-value="2026-11-05T09:58:51+00:00" > 11/05/26, 09:58 </span>
-
Oliver Bartsch commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-11-05T10:00:26+00:00" > 11/05/26, 10:00 </span>Applied in changeset commit:fb1bee8aa574205f0378bbe5362db652d66a1cf1.
-
Christian Hackl commented <span data-processor="relativetime" data-value="2026-11-05T10:06:30+00:00" > 11/05/26, 10:06 </span>
@obartsch can you please look at this https://forge.typo3.org/issues/109825 too? It seems that this goes in the same direction? Thank you!
Christian Hackl wrote:
> – TYPO3_PATH_APP = /httpdocs/myproject
> – TYPO3_PATH_ROOT = /httpsdocs/myproject/public
You are running into this, because such setup is not supported. Those variables are not meant to be changed and for sure not meant
to be set to differ in classic mode.
If you don’t set those, you are not getting these issues, right?