laravel 4: Route to controller when error occurred

Question

I have a problem with laravel 4. I want to handle occurred errors like, 404 Not Found or any other errors. But I want to call a controller when such errors occurs. I've tried this:

App::missing(function($exception)
{
    return Response::view('errors.404', array('error'=>$exception), 404);
});

But actually above code is not my purpose, I want something like this:

//I know this code doesn't work, I've just wanted to show the claim
App::missing('HomeController@error');
App::error('HomeController@error');
// or ...

Is there any way to handle errors within calling a specific controller's method?

Fad · Accepted Answer · 2014-04-06 09:36:41Z

5

Nothing's going to stop you from creating an instance of your controller and calling the method you want to call.

App::missing(function($exception)
{
    return App::make('HomeController')->error($exception);
});

edited Apr 6, 2014 at 9:36

answered Apr 6, 2014 at 9:26

Fad

9,8683 gold badges48 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

The Alpha Over a year ago

Pass the $exception, like return App::make('HomeController')->error($exception);.

Halil Özgür Over a year ago

I'm using this approach but if the request doesn't match any route, I get a 'Call to a member function filter() on a non-object' error (details here). But If the request matches a route but no model is found (e.g. firstOrFail()) it works normally. Any idea?

The Alpha · Accepted Answer · 2014-04-06 09:48:15Z

3

No, you can't use App::missing('Controller@method') directly because the missing method calls error method and that is:

public function error(Closure $callback)
{
    $this['exception']->error($callback);
}

It accepts a closure but you may call a controller->method from the closure. So. declare the handler using a closure as usual and then call a controller's method from within the closure.

As a side note, I don't see any importance to call a method from a controller through/within the closure because you may do the same thing (most probably you'll return a view) from the closure then why just another layer ?

Update:

App::missing(function($e){
    // Use the model here you want
    $var = 'SomeValue' from model
    return Response::view('errors.404', array('error'=> $e, 'another' => $var));
});

edited Apr 6, 2014 at 9:48

answered Apr 6, 2014 at 9:28

The Alpha

147k30 gold badges294 silver badges313 bronze badges

8 Comments

Siamak Motlagh Over a year ago

Actually I'm trying to pass some variables form model to that view. Do you have any suggestion or better solution to do this ?

Siamak Motlagh Over a year ago

You mean I directly write the model inside the router.php and don't pass it to controller ?

The Alpha Over a year ago

Check this article for handling menu/nav bar smartly.

Siamak Motlagh Over a year ago

I'm using the update code which is working fine. But I'll read the article indeed. Thanks.

The Alpha Over a year ago

You may also check laravel-repository-pattern.

|

Collectives™ on Stack Overflow

laravel 4: Route to controller when error occurred

2 Answers 2

2 Comments

8 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

8 Comments

Your Answer

Sign up or log in

Post as a guest

Related