4.1.9 - doesnt seem to be loading the middleware. about laravel-debugbar HOT 9 CLOSED

Any uses why doesnt load the middleware? Do you have the latest debugbar version?

from laravel-debugbar.

Hey Barry… honestly I'm not 100% sure at all, because this would take me a little dissecting, but i do know that Cartalyst/Platform overrides the default Laravel Router / Request / Response stuff, so ill ping the Cartalyst guys and ask them.

On Dec 26, 2013, at 10:01 AM, Barry vd. Heuvel wrote:

Any uses why doesnt load the middleware? Do you have the latest debugbar version?

—
Reply to this email directly or view it on GitHub.

from laravel-debugbar.

Do you have any more info? I read somewhere the Platform updated its API's to 4.1, don't know if that made any difference?

from laravel-debugbar.

Actually, I am on the 4.1 as well, and the problem is still there. Im sorry, I had told you I was going to get a hold of them but I have been super busy, and my quick fix did the trick for the time being… Ill try to get that done.

On Jan 3, 2014, at 8:41 AM, Barry vd. Heuvel wrote:

Do you have any more info? I read somewhere the Platform updated its API's to 4.1, don't know if that made any difference?

—
Reply to this email directly or view it on GitHub.

from laravel-debugbar.

Okay, let me know if you have more info or when it is fixed. Keep it open for now.

from laravel-debugbar.

Closing until someone also has this issue, or it is more clear what the issue was.

from laravel-debugbar.

This can probably be fixed by moving the Debugbar service provider above the Platform one in the array in app.php. See https://github.com/cartalyst/api/issues/34 for a similar issue.

from laravel-debugbar.

Okay so anything I can do? (I can't open the cartalyst issue, not a subscriber..)

from laravel-debugbar.

No, not really. They've also just landed https://github.com/cartalyst/api/pull/35, which fixes the issue and doesn't require user intervention. (I'm not sure if API is causing the Platform issues described above, or if there's a separate fix needed for that.)

But long story short, it's a problem related to overriding the router. So if someone sees this issue again with any package that overrides or extends the router, a possible fix is to move the Debugbar service provider before those packages' providers. That might allow Debugbar to still inject its code in the after filter.

Moving the Debugbar service provider isn't need any longer with today's update to API 2.0-beta, but wanted to share the info here.

from laravel-debugbar.