-
-
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
Error upgrading to Grav 1.7.0-beta.10 #2681
Comments
I can replicate this, trying to upgrade from v1.7.0-beta.4, with the same result. Using Exception trace:
() at C:\Users\olehhu\Web\Grav\system\src\Grav\Common\GPM\Response.php:316
Grav\Common\GPM\Response::getFopen() at C:\Users\olehhu\Web\Grav\system\src\Grav\Common\GPM\Response.php:259
Grav\Common\GPM\Response::getAuto() at C:\Users\olehhu\Web\Grav\system\src\Grav\Common\GPM\Response.php:180
Grav\Common\GPM\Response::get() at C:\Users\olehhu\Web\Grav\system\src\Grav\Console\Gpm\SelfupgradeCommand.php:188
Grav\Console\Gpm\SelfupgradeCommand->download() at C:\Users\olehhu\Web\Grav\system\src\Grav\Console\Gpm\SelfupgradeCommand.php:162
Grav\Console\Gpm\SelfupgradeCommand->serve() at C:\Users\olehhu\Web\Grav\system\src\Grav\Console\ConsoleCommand.php:30
Grav\Console\ConsoleCommand->execute() at C:\Users\olehhu\Web\Grav\vendor\symfony\console\Command\Command.php:255
Symfony\Component\Console\Command\Command->run() at C:\Users\olehhu\Web\Grav\vendor\symfony\console\Application.php:917
Symfony\Component\Console\Application->doRunCommand() at C:\Users\olehhu\Web\Grav\vendor\symfony\console\Application.php:269
Symfony\Component\Console\Application->doRun() at C:\Users\olehhu\Web\Grav\vendor\symfony\console\Application.php:145
Symfony\Component\Console\Application->run() at C:\Users\olehhu\Web\Grav\bin\gpm:72 |
Just upgraded without any problem from v1.7.0-beta.9 to v1.7.0-beta.10 using Grav admin. Running on Linux and Apache. After that upgraded Admin plugin as well to v1.10.0-beta.10. |
Confirmed, this is a bug in all the 1.7.0 beta versions from .4 at least all the way up to .9. |
Fixed with #b4fa7e3 |
1.7.0 has now been released but this will not be fixed until you have 1.7.0-rc.1 or newer installed. It will need to be updated manually until that point. After that things should work again. |
@rhukster Does updated manually mean apply the commited fix manually and then upgrade, or eject everything into a new install? |
Follow these steps to manually update: #2722 (comment) |
The text was updated successfully, but these errors were encountered: