[11.x] Fix PHP_MAXPATHLEN check for existing check of files for views #50962
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Laravel can throw an error
File name is longer than the maximum allowed path length on this platform
, If a string is passed to the functionBlade::render
, which is the same length or slightly shorter than\PHP_MAXPATHLEN
[1]. This happens due to an invalid check for the filename, because the filename gets an prefix (full path) and suffix (e.g..blade.php
) before the existence is checked. This leads to a filename, which is greater than\PHP_MAXPATHLEN
which results in a PHP warning.Thus PHP warning is only thrown, if
open_basedir
[2] is configured [3].[1] https://www.php.net/manual/en/reserved.constants.php#constant.php-maxpathlen
[2] https://www.php.net/manual/en/ini.core.php#ini.open-basedir
[3] https://github.com/php/php-src/blob/7c860628cd2bf11ee867bfb41b3fd0314c5177c5/main/fopen_wrappers.c#L302