FilamentF
Filament•2y ago
_andypeacock

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:

 $plugins = [
            \BezhanSalleh\FilamentShield\FilamentShieldPlugin::make(),
            \Awcodes\Curator\CuratorPlugin::make()
        ];

$panel
            ->id("control")
            ->path("/control")
            ->brandName("Control")
            ->login()
            ->emailVerification()
            ->passwordReset()
            ->colors($colors)
            ->discoverResources(in: app_path('Filament/Resources'), for: 'App\\Filament\\Resources')
            ->discoverPages(in: app_path('Filament/Pages/Mandatory'), for: 'App\\Filament\\Pages\\Mandatory')
            ->pages($pages)
            ->plugins($plugins)
            ->databaseNotifications()
            ->resources($resources)
            ->discoverWidgets(in: app_path('Filament/Widgets'), for: 'App\\Filament\\Widgets')
            ->widgets($widgets)
            ->middleware($middleware)
            ->authMiddleware($authMiddleware)
            ->navigationGroups([
                'Content',
                'Billing',
                'Filament Shield',
            ]);


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?
Was this page helpful?