-
-
Notifications
You must be signed in to change notification settings - Fork 174
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 on create_permissions_table migration #386
Comments
commenting the following lines results in permissions migrations going smoothly
|
I got same issue with create_permission_tables this but the error is different. When I run the php artisan shield:install. Kindly help. ` Call to a member function getResources() on null at vendor\filament\filament\src\FilamentManager.php:335 1 vendor\laravel\framework\src\Illuminate\Support\Facades\Facade.php:357 2 vendor\bezhansalleh\filament-shield\src\FilamentShield.php:121 |
could you submit a repro repo? |
Hello,
When I clone my project to a new dev machine and run migrations (fresh, no database)
I get error on create_permissions_table migration file
I tried to reproduce it with a new laravel / filament / filament shield project - the error came up once and then didnt - I was trying migration again and again with new db etc.
I am using Ubuntu 24.04 on WSL on Windows 11
I have tried both sqlite and mysql databases
If I dont run create_permissions_table migration and run everything else and THEN run create_permissions_table migration it works and no error is thrown.
in this case, the refresh migrate also works - once if the create_permissions_table works, then if I refresh - it works again
I will try to give proper reproduction steps, but if there is anything I can do to fix this, would be great - its an inconvinience, as I can still run it - just that doesnt work on first run and need to rename create_permissions_table migration, then run all my migrations first and then run the create_permissions_table later after renaming it back
The text was updated successfully, but these errors were encountered: