-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade grav 1.7.30 and 1.7.29 servr error 500 #3542
Comments
I found the issue: assets: with this config the Utils::pathinfo return "NULL" that is not accepetd. I need to keep all 3 js. Any suggestion |
@NandoPiz I made the methods less strict, but the issue is that some of the files doesn't exist, which causes the method to return false. Please try CI build, it should work. |
@NandoPiz, Please feedback this solution into your Discourse issue and mark that reply as 'solution'. |
Hi, I’ve an issue during the grav upgrade form version 1.7.25 to version 1.7.30
aftrer the upgrade I receive server error 500.
I’ve done many test and the issue start with versione 1.7.29. I mean until version 1.7.28 all works well but with version 1.7.29 I receive error 500 from server.
The test was done with Open Publishing Space skeleton.
I’ve check error 500 and no problem with .htaccess
Checking the change log from version 1.7.29 I can see:
Added unicode-safe Utils::basename() and Utils::pathinfo() methods
Improved Filesystem::basename() and Filesystem::pathinfo() to be unicode-safe
Made path handling unicode-safe, use new Utils::basename() and Utils::pathinfo() everywhere
If I look in the logs directory I can see grav.log file (see attachment)
In order to solve the issue I've changed
system\src\Grav\Common\Assets.php file on line 201
from:
$extension = Utils::pathinfo(parse_url($asset, PHP_URL_PATH), PATHINFO_EXTENSION);
to
$extension = pathinfo(parse_url($asset, PHP_URL_PATH), PATHINFO_EXTENSION);
I've removed Utils::
error.txt
I didn't understand if this is a bug or problem related to my environment
regards
The text was updated successfully, but these errors were encountered: