Wave Upgrade to Laravel 5.8 and Voyager 1.2
You can download the latest version of Wave which has been updated from Laravel 5.6 to 5.8. Voyager 1.0 has been upgraded to 1.2.
It's a pretty simple update, here are the steps to update. Also documented in the documentation:
Upgrade Steps
- Update DEPENDENCIES
composer update
- Voyager::can function is no longer available (has been replaced)
Inside of the 2 following files: resources/views/themes/bootstrap/layouts/app.blade.php resources/views/themes/uikit/layouts/app.blade.php
Change any instances of
Voyager::can('browse_admin')
to
!auth()->guest() && auth()->user()->can('browse_admin')
- (optional) roles id changed from
integer
tobigInteger
Possible option. In Voyager 1.2 the id
in the roles
table has changed from integer to bigInteger
, so you may need to change role_id
inside of the plans
table to be of type bigInteger
instead of integer
.
Here is the file that was changed: wave\database\migrations\2018_09_22_234251_create_plans_table.php
line 22 was changed from:
$table->integer('role_id')->unsigned()->index('plans_role_id_foreign');
to:
$table->bigInteger('role_id')->unsigned()->index('plans_role_id_foreign');
Enjoy :) Thanks!
Thanks Tony! My knowledge of programming is limited to copy&paste code. So this is what i did to upgrade my existing project:
- download Wave RC10 and unzip the file;
- remove existing wave directory in root of my existing project and remove composer.json;
- copy wave directory and composer.json from Wave RC10 to my existing project;
- update dependencies in CLI [composer update];
- change any "Voyager::can" instances in app.blade.php as described in your upgrade-instructions;
- clear ALL cache in CLI [php artisan optimize && php artisan cache:clear && php artisan route:cache && php artisan view:clear && php artisan config:cache]
the only thing i didnt manage to get working yet is chatter and wave RC9 or RC10. i believe it is a javascript thingy, because i cant create or edit or delete a discussion. every solution that i found about js didnt solve my problem.
+1 @marx This happens on a fresh RC10 install too
@tnylea FYI
all fields are required except Additional Roles, if any field is empty then this bug comes into play.
@marx you are correct