問題描述
我正在遵循 5.1 的官方升級指南到 5.2.第一個小節說:
I'm following the official upgrade guide from 5.1 to 5.2. First sub-section says:
如果您要安裝 Laravel 5.2 的測試版，請添加"minimum-stability": "beta" 到您的 composer.json 文件.
If you are installing a beta release of Laravel 5.2, add
"minimum-stability": "beta"to your composer.json file.
更新您的 composer.json 文件以指向 laravel/framework 5.2.*.
Update your composer.json file to point to laravel/framework 5.2.*.
將 symfony/dom-crawler ~3.0 和 symfony/css-selector ~3.0 添加到composer.json 文件的 require-dev 部分.
Add symfony/dom-crawler ~3.0 and symfony/css-selector ~3.0 to the
require-dev section of your composer.json file.
現在，在我引入上述更改并運行 composer update 后，出現以下錯誤:
Now, after I introduce the above changes and run composer update, I get the following error(s):
PHP Fatal error: Class 'IlluminateRoutingControllerServiceProvider' not found
in /home/vagrant/Code/myproject/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 146
和
[SymfonyComponentDebugExceptionFatalErrorException]
Class 'IlluminateRoutingControllerServiceProvider' not found
和
[RuntimeException]
Error Output: PHP Fatal error: Class 'IlluminateRoutingControllerServiceProvider' 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.
可能有什么問題?
這看起來不像是自定義包問題，而是核心問題.我是否應該繼續升級指南并在所有內容都已調整以適應新框架版本后運行 composer update?
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 不會拋出上述錯誤.不過還是很困惑.
Running composer dump-autoload afterwards doesn't throw the errors described above. Still confusing, though.
推薦答案
不再有IlluminateRoutingControllerServiceProvider.
如果我是你，我會將我的應用項目與 https://github.com/laravel/laravel/commits/develop 進行比較，例如，如果您查看 https://github.com/laravel/laravel/blob/develop/config/app.php 你會看到 Laravel 5.2 的默認提供者:
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:
IlluminateAuthAuthServiceProvider::class,
IlluminateBroadcastingBroadcastServiceProvider::class,
IlluminateBusBusServiceProvider::class,
IlluminateCacheCacheServiceProvider::class,
IlluminateFoundationProvidersConsoleSupportServiceProvider::class,
IlluminateCookieCookieServiceProvider::class,
IlluminateDatabaseDatabaseServiceProvider::class,
IlluminateEncryptionEncryptionServiceProvider::class,
IlluminateFilesystemFilesystemServiceProvider::class,
IlluminateFoundationProvidersFoundationServiceProvider::class,
IlluminateHashingHashServiceProvider::class,
IlluminateMailMailServiceProvider::class,
IlluminatePaginationPaginationServiceProvider::class,
IlluminatePipelinePipelineServiceProvider::class,
IlluminateQueueQueueServiceProvider::class,
IlluminateRedisRedisServiceProvider::class,
IlluminateAuthPasswordsPasswordResetServiceProvider::class,
IlluminateSessionSessionServiceProvider::class,
IlluminateTranslationTranslationServiceProvider::class,
IlluminateValidationValidationServiceProvider::class,
IlluminateViewViewServiceProvider::class,
/*
* Application Service Providers...
*/
AppProvidersAppServiceProvider::class,
AppProvidersAuthServiceProvider::class,
AppProvidersEventServiceProvider::class,
AppProvidersRouteServiceProvider::class,
這篇關于將 Laravel 5.1 升級到 5.2 時出現致命錯誤的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！