-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 via GIT results in Server Error #16334
Comments
Yup, we're working on fixing that - in the meantime, if you run |
If you run |
From the user manual:
https://snipe-it.readme.io/docs/upgrading
|
Doing the git pull first was to make sure you have the updated version of the upgrade.php. I think the problem is running the backup before the composer install, since the backup is done via a package, and will pull from the autoloader. |
@swift2512 I've just changed the order of things in the upgrade script - can you give it a try now (after a git pull so you have the latest version of the upgrader)? |
@snipe upgrade went OK this time, not resulting in Server error, but I got errors on step 5. Here's the log of upgrade script. I clicked through various parts of Snipe-IT install, everything seems to work normally after this upgrade. (Even breadcrumbs) Upgraded from v7.1.15 to v8.0.1.
|
Thank you - this is super helpful. What I think we're seeing here is a problem with the order of operations. :( The script is calling |
@snipe upgrade script went flawlessly, no errors shown in any of steps. |
Excellent, thank you for letting me know. I think I've rearranged the order of things now so you shouldn't run into this again. (I haven't pushed the changes to the upgrade script to develop/master yet, but I think it should work.) |
Signed-off-by: snipe <[email protected]>
so doing same commands in snipe repository, "composer install" then "sudo php upgrade.php" got my server back up and running. really odd, but I suppose going from version 7 to 8 is the reason for it. |
Upgrade from v7.1.16 (build from last week.)
STEP 4: Backing up database:
--
BadMethodCallException
Method Illuminate\Routing\Route::breadcrumbs does not exist.
at vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php:112
108▕ */
109▕ public function __call($method, $parameters)
110▕ {
111▕ if (! static::hasMacro($method)) {
➜ 112▕ throw new BadMethodCallException(sprintf(
113▕ 'Method %s::%s does not exist.', static::class, $method
114▕ ));
115▕ }
116▕
1 routes/web/hardware.php:32
Illuminate\Routing\Route::__call()
+3 vendor frames
5 routes/web/hardware.php:22
Illuminate\Support\Facades\Facade::__callStatic()
Something went wrong with your backup. Aborting!
Same with php artisan config:clear
BadMethodCallException
Method Illuminate\Routing\Route::breadcrumbs does not exist.
at vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php:112
108▕ */
109▕ public function __call($method, $parameters)
110▕ {
111▕ if (! static::hasMacro($method)) {
➜ 112▕ throw new BadMethodCallException(sprintf(
113▕ 'Method %s::%s does not exist.', static::class, $method
114▕ ));
115▕ }
116▕
1 routes/web/hardware.php:32
Illuminate\Routing\Route::__call()
+3 vendor frames
5 routes/web/hardware.php:22
Illuminate\Support\Facades\Facade::__callStatic()
The text was updated successfully, but these errors were encountered: