Plugin [awcodes/curator] is not registered for panel [admin]
Hi,
After some issues with stancl/tenancy and fileupload (which I resolved by removing the stancl package), I've got file upload working, and decided to play with awcode's curator plugin. However, I'm getting the above error (which I don't think is a curator issue).
I have two panels: control and admin. I'm trying to use the plugin only in the control one, which has config as follows:
I'm on the /control route, and the panel is displaying the brandname "control", and the plugin is listed if I do $panel->getPlugins()
If I enable the plugin on the /admin panel, it then starts to work in /control, but I can't work out why filament is getting confused about the panel.
I've search ControlPanelProvider.php and the Curator repo for "admin", and the word isn't used, so it's not like something is hard-coded...
Any one seen this before?
11 Replies
I’ve noticed this too. Have created a reproduction repo for Dan and he is aware of it.
Ah, ok, thanks again @awcodes !
I'll include it in /admin for now until the issue is resolved.
You can also disable the navigation for it in admin to “hide” it on that panel.
Hi @awcodes - how do you disable the navigation for it on a specific panel? I've had a poke around but can't see an obvious way of doing that.
I don’t think you can currently since it’s a config setting. Give me a day and I’ll see what I can do.
to resolve this, change panel provider order in /conf/app.
This might work, but there’s an underlying issue in filament. I believe it has to do with the panel navigation not compensating for plugins that may or may not be registered on the panel.
Here the reproduction repo if you have time to try to figure it out. https://github.com/awcodes/filament-panels-plugin-bug
GitHub
GitHub - awcodes/filament-panels-plugin-bug
Contribute to awcodes/filament-panels-plugin-bug development by creating an account on GitHub.
I'm facing the same issue, using just one panel and three filament plugins
This throws an error (Plugin [filament-shield] is not registered for panel [admin]):
And this works as expected:
->plugins([])
ufff