'Illuminate\Foundation\Support\Providers\FilterServiceProvider' not found

This file was removed from the repository, for more information:

https://github.com/laravel/framework/tree/master/src/Illuminate/Foundation/Providers

Those are the latest Service Providers that exist within the providers path.

When I try composer update I also got same error like the following

PHP Fatal error: Class 'Illuminate\Foundation\Support\Providers\FilterServiceProvider' not found in laravel5/app/Providers/FilterServiceProvider.php on line 5

With those changes, I always recommend to make a backup of your project folder before run composer update, because some changes crashes your application.

Seems I am bouncing from error to error:

"message":"Class 'App\\Providers\\FilterServiceProvider' not found","file":"/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/ProviderRepository.php","line":157}}

This will teach me for using beta software!!

Update your project by looking at the updates made on October 5 and 6th

https://github.com/laravel/laravel/compare/develop

Look at this commit specifically and the comments on the commit. This should help you out.

https://github.com/laravel/laravel/commit/17ac063e80e599d5d21b4515d7505f9a15a11d66

It's removed from compile list.

https://github.com/laravel/laravel/commit/84b8a7c88ba388030fe46511fa6b6e305a6ad922

I still got an error.

Yeah this problem stopped my pending projects and now I regret using non-stable version. However L5 is so much better compared to 4...

According to this I removed FilterServiceProvider from config/app.php and I got an new error on

/­vendor/­laravel/­framework/­src/­Illuminate/­Container/­Container.php56

Function () does not exist It's still same errors with me?

Same here...

did you run a git update on the Laravel app itself and not just a composer update?

No, I ran composer update...when I cd to src/vendor/laravel/framework and git pull I get a message that says: Already up-to-date.

I thought composer update DOES a git pull?

no, not git pull on illuminate.... There are two parts to laravel... laravel/laravel, this is your app folder structure (app, bootstrap, config, etc...) and then illuminate framework... You need to keep the laravel/laravel updated as well. This is a git update, not a composer update.

There seems to be a few updates that will break the latest update,you need to do the following to get rid of some of the errors;

remove 'App\Providers\FilterServiceProvider' from the app.php file remove 'use Illuminate\Routing\Controller;' from your controllers remove 'extends Controller' from your controllers

I know its a bit mad crazy but Taylor seems to had mad the 'controller class' autoload

I am loving this bleeding edge stuff, it's why I became a developer, and Laravel is getting better every day not just every release.

Yah I have taken both of those steps and still have this exception when I try to load the page:

ReflectionException Function () does not exist Open: /src/vendor/laravel/framework/src/Illuminate/Container/Container.php { if (is_array($callback)) { return new ReflectionMethod($callback[0], $callback[1]); } else { return new ReflectionFunction($callback); } }

1. ReflectionException …/­vendor/­laravel/­framework/­src/­Illuminate/­Container/­Container.php564
2. ReflectionFunction __construct …/­vendor/­laravel/­framework/­src/­Illuminate/­Container/­Container.php564
3. Illuminate\Container\Container getCallReflector …/­vendor/­laravel/­framework/­src/­Illuminate/­Container/­Container.php542
4. Illuminate\Container\Container getMethodDependencies …/­vendor/­laravel/­framework/­src/­Illuminate/­Container/­Container.php526
5. Illuminate\Container\Container call …/­vendor/­laravel/­framework/­src/­Illuminate/­Foundation/­Application.php714
6. Illuminate\Foundation\Application run …/­public/­index.php49

https://github.com/laravel/laravel/tree/develop/app/Http Seems you need to remove the filters folder. Although I was then getting a HTTP error.

Technically @joshuahornby, Laravel 5 isn't even in alpha yet. ;)

Yeah, but isn't it exciting to see this stuff unfold and it really does make you read the doc more closely, well at least it does for me anyway :)

Oh absolutely, there've been about a dozen times where I see something he's done and gone "awww man, why didn't I think of that?"

I had the "ReflectionException Function () does not exist" error as well, and after a lot of struggling I managed to sort it. In my case the problem was the config/local/app.php file.

In there I had also a couple ServiceProviders that I don't need on the live server (like the way/generators and the laravel-ide-helper) and everything was working fine. After doing the composer update I just couldn't get around this problem, until I finally emptied the config/local/app.php file and left just the debug=>true For some reason the last commit of laravel is not merging the 'providers' array anymore, and it looks like is replacing it instead. let me know if it helped solving your problem as well!

Currently all is fixed as of now.

The problem was that "laravel/laravel" is not a dependency so composer update doesn't pull down the changes that were made to the app folder for example. e.g. the "Middleware" folder was missing entirely from the Http folder. You need to do apply these changes manually on an existing app.

I added the middleware folder to HTTP from laravel/laravel...still doesn't work. I must be missing something obvious, but am missing it nonetheless. I looked at config/app.php and don't see any service providers being requested that aren't there.

Did you check you LOCAL config? What's the content of the config/local/app.php (or the one being used by your environment)? In my case I had to remove the providers array in that file to make it work again.

@jcorry did you merge all changes made by Taylor from the moment you created your L5 project? https://github.com/laravel/laravel/compare/develop

OK, in config/app.php remove 'App\Providers\FilterServiceProvider'.

Delete app/Filters folder.

Add the new app/Middleware folder and files.

Replace all files in app/Providers with latest ones and delete FilterServiceProvider.php.

Finally your controllers no longer extend Controller so remove "use Illuminate\Routing\Controller;" and "extends Controller" from your controllers.

<?php namespace App\Http\Controllers;

class HomeController { 

     /*
     |--------------------------------------------------------------------------
     | Default Home Controller
     |--------------------------------------------------------------------------
     |
     | You may wish to use controllers instead of, or in addition to, Closure
     | based routes. That's great! Here is an example controller method to
     | get you started. To route to this controller, just add the route:
     |
     |  $router->get('/', 'HomeController@index');
     |
     */

     /**
      * @Get("/", as="home")
      */
     public function index()
     {
          return view('hello');
     }

}

I think that should do it.

sitesense, thanks a million. It looks like it's working.

Looks like

use Illuminate\Routing\Controller;

and

extends Controller {

is back in the latest version.

Although after stepping through all the changes at laravel/laravel my app is still broken.. time to go a-hunting!

Interestingly I needed to prefix the full controller namespace in my routes.php groups and that seemed to fix it. I know it's all about annotations now, but I haven't quite caught up that far as of yet.

Strangely with the latest update (CSRF in Middleware) Codeception POST/PUT functional tests all fail with CSRF mismatch exceptions