Class 'CRUD' not found during package:discover about settings HOT 5 CLOSED

Yes. I've this issue too, on some projects, because Laravel try to load backpack-setting before backpack-crud. According to me, you have to move this line in the boot() section : https://github.com/Laravel-Backpack/Settings/blob/master/src/SettingsServiceProvider.php#L82

Laravel documentation mentions this:

You should never attempt to register any event listeners, routes, or any other piece of functionality within the register method. Otherwise, you may accidentally use a service that is provided by a service provider which has not loaded yet.

https://laravel.com/docs/5.5/providers

from settings.

oh, I take the suggested fixes back - after trying to run the admin interface in browser the issue came back. What I really did to work around it (this time for real I guess) was to put backpack/settings into dont-discover section in main composer.json file and load the Backpack\Settings\SettingsServiceProvider::class manually in config/app.php

from settings.

Huh... this is odd. Just updated a project to test, then installed it on a fresh laravel - no such issue in my experience.

I wonder if the problem isn't the order, as defined in composer.json - is your settings requirement BEFORE the crud requirement?

Cheers!

from settings.

@tabacitu the order seems to be correct (it was the first thing I've checked)

"require": {
        "php": ">=7.0.0",
        "backpack/base": "^0.8.0",
        "backpack/crud": "^3.3.0",
        "backpack/settings": "^2.0",
        ...
}

The weird thing is, I've tried to revert my changes back to the default state and now everything works without any issue.

Despite that, @jguyomard's suggestion seems to be correct and should solve this behaviour in the end, so we can probably close this issue after merging his PR.

Thanks!

from settings.

Hi guys,

Just merged @jguyomard 's PR. Please reopen this issue if after a composer update you're still having this problem.

Cheers!

from settings.