I have a simple laravel project with migrations that work fine. I want one of them to start first (so I can use this table to restrict the foreign key during subsequent migration), so I renamed this porting script by adding “1_” to be the first in the list.
But when I start migrations from the moment the file is renamed, I get a fatal "class not found" error for class 152152CreatePeopleTable, from Migrator.php on line 324 - see the full stack trace below. (And when I rename the migration file back, the class will be found again when the migration is performed).
I updated the name in vendor / composer / autoload_classmap.php to match the updated file name (1_2015_09_06_152152_create_people_table.php) and the search in phpstorm, '152152_create_people' was not found anywhere except laravel.log, so there could be no old name file, right?
So, I cleared the cache and tried other recommendations from similar problems (thanks google / stackoverflow):
- php artisan cache: clear
- composer clearcache
- composer dumpautoload
- composer update just in case
- I made sure that I also had a table with new migrations; I deleted ALL from my database tables (including migrations), then executed "php artisan migrate: install" (to create a new migration table) and "php artisan migrate" to make sure everything is running completely fresh, still the same mistake
- hail mary: , autoload classmap composer.json, ( , ): ", " -? Laravel 4
- . sqlite , postgres. Juuust , , database.php, sqlite .
/?
[2015-09-12 22:42:19] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Class '152152CreatePeopleTable' not found' in /home/vagrant/Code/Family-laravel/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:324
Stack trace: