Skip to content
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

1.7 Upgrade error #3160

Closed
NicoHood opened this issue Jan 20, 2021 · 2 comments
Closed

1.7 Upgrade error #3160

NicoHood opened this issue Jan 20, 2021 · 2 comments
Assignees

Comments

@NicoHood
Copy link
Contributor

$ ./bin/gpm selfupgrade

GPM Releases Configuration: Stable

Grav v1.7.0 is now available [release date: Tue Jan 19 21:13:42 2021].
You are currently using v1.6.31.
Would you like to read the changelog before proceeding? [y|N] 
Would you like to upgrade now? [y|N] y

Preparing to upgrade to v1.7.0..
  |- Downloading upgrade [12.44M]...   100%
  |- Installing upgrade...    ok                             
  '- Success!  

PHP Fatal error:  Uncaught Error: Call to undefined method Grav\Console\Cli\ClearCacheCommand::initializeGrav() in /home/user/grav/system/src/Grav/Console/GravCommand.php:33
Stack trace:
#0 /home/user/grav/vendor/symfony/console/Command/Command.php(255): Grav\Console\GravCommand->execute()
#1 /home/user/grav/system/src/Grav/Console/ConsoleTrait.php(112): Symfony\Component\Console\Command\Command->run()
#2 /home/user/grav/system/src/Grav/Console/Gpm/SelfupgradeCommand.php(186): Grav\Console\ConsoleCommand->clearCache()
#3 /home/user/grav/system/src/Grav/Console/ConsoleCommand.php(41): Grav\Console\Gpm\SelfupgradeCommand->serve()
#4 /home/user/grav/vendor/symfony/console/Command/Command.php(255): Grav\Console\ConsoleCommand->execute()
#5 /home/user/grav/vendor/symfony/console/Application.php(917): Symf in /home/user/grav/system/src/Grav/Console/GravCommand.php on line 33
@mahagr mahagr self-assigned this Jan 20, 2021
@mahagr
Copy link
Member

mahagr commented Jan 20, 2021

Yeah, it looks like it's not a good idea to call another CLI command after the underlying files have been replaced.

@mahagr
Copy link
Member

mahagr commented Jan 20, 2021

The upgrade itself did not fail, the command just failed to clear the cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants