TYPO3 Core

Hi,

same too:

Core: Error handler (BE): PHP Warning: file_exists(): open_basedir restriction in effect. File(/typo3/sysext/form/Resources/Public/Css/form.css) is not within the allowed path(s): (/home/users/internet/www:/home/users/ja-internet/files:/home/users/internet/tmp:/usr/bin/) in /home/users/internet/www/tools/_t3src/11/typo3_src-11.5.17/typo3/sysext/core/Classes/Utility/GeneralUtility.php line 2317

EXT:form/Resources/Public/Css/form.css will be loaded bei Chrome.

• Upgare from 10.5 to 11.5.17 (classic mode)
• EXT:form installed
• php.ini (PHP 7.4) with open_basedir set to "/home/users/internet/www"
• LocalConfiguration.php with BE/debug=false, and versionNumberInFilename=false, display_errors=0

If Preset Configuration Debug is true the error ist still not there.

I ran into the same log entries today in a 11.5.24 on PHP 7.4 as mentioned here and in #98330 for other extensions - I see two important points:

A) The value of open_basedir is irrelevant¶

For some reason the check is done for /typo3/sysext/... or /typo3conf/ext/... paths, so basically a frontend url path segment and not a local file prefixed with Environment::getPublicPath().
So the check in itself should not be done in that way because either it should not be done with file_exists as it is a frontend path, or the prefix needs to be in place.

B) Why is the warning not supressed?¶

L2158 is a file_exists in a TRY block with pokemon exception handling for exceptions

        try {
            $fileExists = file_exists($path);
        } catch (\Throwable $e) {
            $fileExists = false;
        }

(will look into the actual extension call stack as soon as I get time to identify the reason why a wrong call is done as mentioned in (A))

TYPO3 11.5.28
PHP 8.1.20

Don't know if this is the same, but in news_administration -> default Template:

<f:asset.css identifier="news_administration" href="EXT:news_administration/Resources/Public/Css/Backend/administration.css" />

CSS is loaded:

Protocol: PHP Warning: file_exists(): open_basedir restriction in effect. File(/typo3conf/ext/news_administration/Resources/Public/Css/Backend/administration.css) is not within the allowed path(s).

I think <f:asset> is not working as it should.

B) Why is the warning not supressed?¶

L2158 is a file_exists in a TRY block with pokemon exception handling for exceptions

[...]
However it raises a WARNING and thus won't be catched would it? So the behaviour is undesirable (as in: drop the WARNING please) but still the WARNING is according to code isn't it?

The behaviour depends on SYS.exceptionalErrors. If you want TYPO3 to convert Warnings to Exceptions, the try..catch block does make sense and you simply ignore the issue. That's funny because if you want to have less issues being converted to exceptions, you get the undesired effect of a flooded backend log because warnings are logged there.

That's funny because if you want to have less issues being converted to exceptions, you get the undesired effect of a flooded backend log because warnings are logged there.

That's why I wondered. And having warnings as warnings is/should probably be default.

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82635

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82635

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82635

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82635

Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82616

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82617

Patch set 2 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82617

Patch set 3 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82617