Closed 06tech closed 1 year ago
I got the same issue
@06tech @papipsycho what version of Filament are you using?
Version v3.0.27
Did you add BreezyCore::make()
to your AdminServiceProvider before it was installed? It would appear that Filament is trying to read a plugin that hasn't been installed/discovered yet.
Btw i downgrade to the version 2.1.4 of breezy and seem better
Did you add
BreezyCore::make()
to your AdminServiceProvider before it was installed? It would appear that Filament is trying to read a plugin that hasn't been installed/discovered yet.
Nop, i was thinking to do that after the composer require / install
v3.0.27
Ok so the issue, seems come from the version 2.1.5, cause with 2.1.4 is work like a charme
What happens when you try composer update
?
There's nothing in v2.1.5 that would prevent the package from being discovered.
Did you add
BreezyCore::make()
to your AdminServiceProvider before it was installed? It would appear that Filament is trying to read a plugin that hasn't been installed/discovered yet.Nop, i was thinking to do that after the composer require / install
Same goes for me - the Breezy install is supposed to happen after the composer require right? Exception seems to be coming from your routes/web.php
I checked the diff between the 2.1.5 and 2.1.4 and i really didn't understood why we got this issue,
here the video of installer 2.1.5 vs 2.1.4
I forget the url : https://youtu.be/-BcYq4Vni0g
I checked the diff between the 2.1.5 and 2.1.4 and i really didn't understood why we got this issue,
here the video of installer 2.1.5 vs 2.1.4
It looks like the Breezy routes/web.php is getting loaded/called by Laravel or Filament before the plugin has been installed and the Breezy route is calling one of it's own plugin functions .. so as it hasn't been installed -> Exception... or something like that...
Can you both try composer update now?
yea for me composer require jeffgreco13/filament-breezy
- completes now with no exception anymore. Thanks for the quick resolution.
Installing this plugin on a v3 Filament site throws the following exception. Afterwards the site won't load anymore - throwing the same exception.