cannot run migrate:fresh after setup

[rasyidialwee]

hello i manage to install and use laravel-setting package. however when i try to run php artisan migrate:fresh it show error
Base table or view not found: 1146 Table 'reacx.settings' doesn't exist (SQL: select name, payloadfromsettingswheregroup = system)

[rubenvanassche]

Hi @rasyidialwee,

You should first publish the settings migration that was supplied with the package(https://github.com/spatie/laravel-settings/blob/master/database/migrations/create_settings_table.php.stub). Be sure to add this migration before any settings migration since this one will create the settings table, the other settings migrations will only add items to this table.

[rasyidialwee]

i already publish my setting. each time i try to run php artisan now stuck at Base table or view not found: 1146 Table 'reacx.settings' doesn't exist (SQL: select `name`, `payload` from `settings` where `group` = system)

…

On Tue, Mar 30, 2021 at 5:02 PM Ruben Van Assche ***@***.***> wrote: Closed #54 <#54>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFOVHKN53ADDEG7UIEH6SK3TGGHSFANCNFSM4Z7G7DEQ> .

-- *Rasyidi Alwee* *Software Engineer*

[rasyidialwee]

nevermind i notice the error is caused by using Setting class on a route. fixed it by using if(class_exists('ClassName')) Thank you On Thu, Apr 1, 2021 at 12:12 AM Rasyidi Alwee ***@***.***> wrote:

…

i already publish my setting. each time i try to run php artisan now stuck at Base table or view not found: 1146 Table 'reacx.settings' doesn't exist (SQL: select `name`, `payload` from `settings` where `group` = system) On Tue, Mar 30, 2021 at 5:02 PM Ruben Van Assche ***@***.***> wrote: > Closed #54 <#54>. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#54 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFOVHKN53ADDEG7UIEH6SK3TGGHSFANCNFSM4Z7G7DEQ> > . > -- *Rasyidi Alwee* *Software Engineer*

-- *Rasyidi Alwee* *Software Engineer*

[chengkangzai]

got same problem and just wanna say thanks to dropping the fix !

If anyone come across this problem, checkout your backtrace from laravel.log to see which class is using the class and use class_exists(Setting::class) to ensure the class exist before you call it !