Fatal error while upgrading Laravel 5.1 to 5.2
I'm following the official upgrade guide from 5.1 to 5.2. First sub-section says:
If you are installing a beta release of Laravel 5.2, add
"minimum-stability": "beta"to your composer.json file.
Update your composer.json file to point to
symfony/css-selector ~3.0to the require-dev section of your composer.json file.
Now, after I introduce the above changes and run
composer update, I get the following error(s):
PHP Fatal error: Class 'Illuminate\Routing\ControllerServiceProvider' not found in /home/vagrant/Code/myproject/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 146
[Symfony\Component\Debug\Exception\FatalErrorException] Class 'Illuminate\Routing\ControllerServiceProvider' not found
[RuntimeException] Error Output: PHP Fatal error: Class 'Illuminate\Routing\ControllerServiceProvider' not found in /home/vagrant/Code/myproject/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 146
The errors are thrown after the update is done, and "Generating autoload files" takes place.
What might be wrong?
It does not look like a custom package issue, but a core one. Should I continue with the upgrade guide and run
composer update AFTER all has been adjusted to suit the new framework version?
composer dump-autoload afterwards doesn't throw the errors described above. Still confusing, though.
There is no
Illuminate\Routing\ControllerServiceProvider any more.
If I were you, I would compare my app project to
https://github.com/laravel/laravel/commits/develop, if you for example look at
https://github.com/laravel/laravel/blob/develop/config/app.php you will see default providers for Laravel 5.2:
Illuminate\Auth\AuthServiceProvider::class, Illuminate\Broadcasting\BroadcastServiceProvider::class, Illuminate\Bus\BusServiceProvider::class, Illuminate\Cache\CacheServiceProvider::class, Illuminate\Foundation\Providers\ConsoleSupportServiceProvider::class, Illuminate\Cookie\CookieServiceProvider::class, Illuminate\Database\DatabaseServiceProvider::class, Illuminate\Encryption\EncryptionServiceProvider::class, Illuminate\Filesystem\FilesystemServiceProvider::class, Illuminate\Foundation\Providers\FoundationServiceProvider::class, Illuminate\Hashing\HashServiceProvider::class, Illuminate\Mail\MailServiceProvider::class, Illuminate\Pagination\PaginationServiceProvider::class, Illuminate\Pipeline\PipelineServiceProvider::class, Illuminate\Queue\QueueServiceProvider::class, Illuminate\Redis\RedisServiceProvider::class, Illuminate\Auth\Passwords\PasswordResetServiceProvider::class, Illuminate\Session\SessionServiceProvider::class, Illuminate\Translation\TranslationServiceProvider::class, Illuminate\Validation\ValidationServiceProvider::class, Illuminate\View\ViewServiceProvider::class, /* * Application Service Providers... */ App\Providers\AppServiceProvider::class, App\Providers\AuthServiceProvider::class, App\Providers\EventServiceProvider::class, App\Providers\RouteServiceProvider::class,
php - Fatal error while upgrading Laravel 5.1 to 5.2, There is no Illuminate\Routing\ControllerServiceProvider any more. If I were you, I would compare my app project to Questions: I’m following the official upgrade guide from 5.1 to 5.2. First sub-section says: If you are installing a beta release of Laravel 5.2, add "minimum-stability": "beta" to your composer.json file.
In updating from 5.1 to 5.2 on existing projects, we found that running
composer update before and after the removing the lines for the providers
was a necessary sequence to getting the laravel update to complete.
Running before would allow laravel to download and update the current framework library dependencies and then running after the removal (composer was able to complete without issue)
We also found that any value in the .env file cannot have spaces and must be surrounded with quotes to work.
Upgrading from 5.1 to 5.2 fatal error, I am updating from 5.1 to 5.2, and was following along in the upgrade docs, bindShared has been changed to singleton in the This must be new as of Laravel 5.2 or something because I've never had an issue before. Yes, that's a consequence of us upgrading from phpdotenv 1.x to 2.x. This comment has been minimized.
Remove the two service providers from config/app.php
Fatal error while upgrading Laravel 5.1 to 5.2, If you are installing a beta release of Laravel 5.2, add "minimum-stability": "beta" to your composer.json file. Update your composer.json file to Just weighing in as I hit this same issue. This is technically not a bug, but a side-effect of the value for the morph_type field being an empty string ('') instead of a proper null.
Updating the app.php file under config/ solved one problem but with the introduction of the bootstrap/cache folder you will probably continue running into the same error.
I ran the composer update Before removing the cached file so I kept hitting the same error. Make sure that you delete the bootstrap/cache/services.php file first.
There might be a artisan command for this but I totally missed this step in the documentation.
Upgrade Guide - Laravel, Not doing so can trigger an error when running in 5.1., you may update your code like so for 5.2. I have this issue. I've had no issues under ubuntu 16 + php.7.0 + laravel 5.5, but now under ubuntu 18 it seems to non-deterministicly break php artisan dusk (running all tests).
I found the solution here:
The Illuminate\Foundation\Providers\ArtisanServiceProvider should be removed from your service provider list in your app.php configuration file.
The Illuminate\Routing\ControllerServiceProvider should be removed from your service provider list in your app.php configuration file.
Fatal error while upgrading Laravel 5.1 to 5.2, Update your composer.json file to point to laravel/framework 5.2.* . Add symfony/dom-crawler ~3.0 and symfony/css-selector ~3.0 to the require-dev section of Join GitHub today. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
[5.1] [5.2] Composer update issues · Issue #9678 · laravel/framework , [L5] Fatal error in clear-compiled command #8665. Closed [Migration][laravel 5.1->5.2][php artisan clear-compiled is not known] #1. Open. Dismiss Join GitHub today. GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
laravel update from 5.1 to 5.2 composer update error , laravel update from 5.1 to 5.2 composer update error. I am trying to update laravel from 5.1 to 5.2 . as according to update doc but I am getting this error when running composer udpate: Error Output: PHP Fatal error: Call to undefined method Laravel is built with testing in mind. In fact, support for testing with PHPUnit is included out of the box and a phpunit.xml file is already set up for your application. The framework also ships with convenient helper methods that allow you to expressively test your applications. By default, your application's tests directory contains two
While upgrading 5.1 to 5.2, Forum > While upgrading 5.1 to 5.2. Vimal10 posted 4 years ago FatalErrorException in BusServiceProvider.php line 16: Call to undefined Once VirtualBox / VMware and Vagrant have been installed, you should add the laravel/homestead box to your Vagrant installation using the following command in your terminal. It will take a few minutes to download the box, depending on your Internet connection speed: vagrant box add laravel/homestead