-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[v6] There is no permission named '1' for guard 'web'. #2543
Comments
Seems like the same #2530 (comment) (again) laravel-permission/docs/upgrading.md Line 35 in bd077c8
|
The link doesn't work |
whatever***
for guard web
.**
whatever***
for guard web
.**
Dear contributor, because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it. |
for whoever comes here, here is how i solved it. it might not be the most efficient but it works in a pinch:
|
Describe the bug
I'm using basic spatie settings for controlling roles&permissions in my laravel 10 project.
The issue is that I keep facing :
which happened since upgrading to v6-6.0.1 while using standard commands such as
also I'm using default laravel 'web' guard.
When I'm downgrading to V5.11 or 5.8 I get no error and everything works perfectly !
Versions
You can use
composer show
to get the version numbers of:PHP version:
8.2.4
Database version:
MariaDB 10.4.28
To Reproduce
Steps to reproduce the behavior:
Here is my example code and/or tests showing the problem in my app:
&
Example Application
Here is a link to my Github repo containing a minimal Laravel application which shows my problem:
https://github.com/falkonerX72/L.estate
Environment (please complete the following information, because it helps us investigate better):
The text was updated successfully, but these errors were encountered: