I\'m working on a CMS and I have a little problem with my migrations. I added a new migration file and I wanted to add that one. That didn\'t work so I ran this bit:
You can use this to dictate when your app is running from the console. I believe this issue only occurs when you run a command
if( !App::runningInConsole() ){
//allow laravel-menu to run
}
This way you will prevent data load from your non-existent table
Remove any lines requesting data from your model from these files to be sure artisan is not trying to load data from your non-existent table:
bootstrap/start.php
app/start/global.php
app/start/local.php
app/routes.php
Also be sure to un-register any service providers that utilize data from that table in their register or boot methods inside of app/config/app.php
.
The issue is that these files not only get executed for browser (web) requests, but for all requests, including command-line artisan invocations (e.g. php artisan migrate
). So if you try to use something before it is available in any of these files, you are going to have a Bad Time.