Laravel Fatal Error Class Not Found when migrating

Question

1. I've run artisan migrate:reset.
2. I've deleted some of my migration files because I didn't need these tables anymore.
3. I ran composer dump-autoload followed by artisan dump-autoload

4. I ran artisan migrate and I keep getting this error:

   PHP Fatal error: Class 'Foo' not found in /vagrant/LaravelBackend/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php on line 297

I tried to:

• Run again composer dump-autoload and artisan dump-autoload (also used artisan clear-compiled)
• Remove the migration table and run artisan migrate:install
• Remove the vendor and composer.lock file and run composer install

• Search within my project with PHPStorm for class Foo. Didn't find anything.

  I keep getting the same error. It's the first time I run this since I updated to 4.2 if that could be related. Anything else I should be looking for?

Answer 1

I had this problem too. Must remember: class name must be in accordance with filename. Simple file renaming helped me:)

For example: in file "2014_12_08_100923_create_items_tables.php" must be class with name "CreateItemsTables" with using CamelCase words.

Answer 2

I solved my problem by

1. Removing all migration
2. Running composer dump-autoload
3. Adding them back one by one and running php artisan migrate
4. Deleting those that caused Laravel to throw an error
5. Create new migrations to replace the deleted ones

I'm not sure why that worked but my guess is that I might have modified the class name of these problematic migrations in the past.

I also found that renaming the migration with its initial name (The one throwed with the fatal error) also works for some of them.

Answer 3

I ran into this aswell and the solution was different to all of the above. The reason it was failing was because the filename was still mentioned in the migrations table of the DB. Because there were no unique columns I couldn't remove it with PHPMyAdmin and had to tak the CLI route.

Login to your server as root. Type the following:

mysql -p database_name

(it now prompts for your password. From here on out everything is preceded with mysql > which just means that you're in the Mysql environment.

select * from migrations;

Look for the migration file you removed and copy the name.

delete from migrations where migration = '2015_07_21_000119_create_some_table';

It should mention something about 1 row affected. Now verify that it's gone by typing the first command again:

select * from migrations;

If it's gone exit the Mysql environment by typing

exit;

Now try 'php artisan migrate:rollback' again and it should work like a charm :-)

Answer 4

There is an easier way.

1. Recreate those delete migrations manually. artisan make:migration
2. run artisan migrate:reset to rollback
3. Delete those dummy migations files just created.
4. run artisan migrate:refresh

Answer 5

I know this is a bit past but there is a better way actually. Run the following in terminal and feel free yourself to remove any of them:

~$ php artisan clear-compiled;php artisan cache:clear;php artisan config:clear;php artisan debugbar:clear;php artisan view:clear;php artisan optimize

To do it a regular task create an executable file named artisan-clear:

#!/bin/bash

php artisan clear-compiled
php artisan cache:clear
php artisan config:clear
php artisan debugbar:clear
php artisan view:clear
php artisan optimize

Answer 6

The actual solution is to use the correct naming for your translations. You still may need to do a

composer dump-autoload

The migration files must be as follows YYYY_MM_DD_000000_create_some_table.php and the class name inside must be

class CreateSomeTable extends Migration{}

Answer 7

For me, the solution was that my class name inside the migration somehow started with a lowercase letter. When I changed the class name to be all upper case, then ran a composer dump-autoload, it ended up working for me. This is using Laravel 5.1, for what it's worth.

Answer 8

I did like this: 1. Deleted row non exist migration from migrations table from database 2. And run the command php artisan migrate:refresh

This helped to solve my problem.

*all your data will deleted from database tables

Answer 9

version 5.1.3 same problem fix it me:

• drop database all tables
• php artisan migrate:status

output: No migrations found. ok use it

• php artisan migrate:install
• php artisan migrate

output is:

Migrated: 2016_11_24_093015_dt_some_table
Migrated: 2016_12_05_141004_dt_some_table
Migrated: 2016_12_07_110518_dt_some_table
Migrated: 2016_12_08_141807_dt_some_table
Migrated: 2016_12_13_090832_dt_some_table

this problem is solved

Answer 10

I had the same problem. When I was hiting php artisan migrate:reset, I got Class 'CreateImagesTable' not found. And composer dump-autoload didn't help.

My solution was very easy:

1. php artisan make:migration create_images_table --create=images
2. composer dump-autoload
3. Then I got: SQLSTATE[HY000]: General error: 1 no such table: images (SQL: drop table "images")
4. so in sqlite I typed: CREATE TABLE `images` ( ...> `id` INTEGER ...> );
5. And then php artisan migrate:reset
6. Now I'm happy again

Answer 11

If artisan doesn't work at all and keeps throwing you this message no matter the command you give, delete the config.php file from bootstrap/cache folder.

After that run again

php artisan config:cache