Laravel different controller for route if authenticated?

Question

I tried this:

Route::get('/', 'PageController@getIndex');
Route::group(array('before' => 'auth'), function(){
    Route::controller('/',            'HomeController'); 
});

But it is always requiring login.

I want the PageController@getIndex to be called when visiting '/' when logged in, and HomeController (@getIndex) otherwise.

I know I could set up a redirect, but I'd like to just handle it all within routing.

Yeah I am not sure if this way is possible. You have two locations assigned to the same route location, and declare that you want auth before reaching that location. You could use nested views in the home page and require Auth::check() before the login view and else to the normal home page or something. Otherwise I don't know if you would be able to route 2 separate pages to the same location. — nickcoffey
– nickcoffey, Commented Jun 21, 2013 at 1:26

Hailwood · Accepted Answer · 2013-06-21 05:22:52Z

1

You need to setup your own auth filter

if(!Auth::check()){
    return Route::get('/', 'PageController@getIndex');
} else {
    Route::controller('/',            'HomeController'); 
}

edited Jun 21, 2013 at 5:22

answered Jun 21, 2013 at 5:13

Hailwood

93.2k112 gold badges275 silver badges425 bronze badges

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

1 Comment

Dwight Over a year ago

It's worth keeping in mind that this won't work if you use route caching in the later versions of Laravel (I believe 5.1 and up ship with that feature).

Collectives™ on Stack Overflow

Laravel different controller for route if authenticated?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related