Laravel 4 routing to controller method

Question

I'm currently trying to route as follows:

If user GETs /account/
- If session has account_id, user is logged in; show his account information
- If not, user is not logged in; show login/create form
If user POSTs /account/
- If input has create, user wants to create account; create it
- If not, user wants to login; find his account and go again to /account/

My routes are set this way:

Route::get('account', function() {
    if (Session::has('account_id'))
        return 'AccountsController@show';
    else
        return 'AccountsController@index';
});

Route::post('account', function() {
    if (Input::has('create')) {
        return 'AccountsController@create';
    else    
        return 'AccountsController@login';
)};

This is somewhat how I would do with Rails, but I don't know how to point to the controller method. I just get the returned string as a result. I didn't find it in Laravel documentation (which I found really poor, or have I searched wrong?) neither in any other web tutorial.

I didn't tried but, this one may help you: laravel.com/api/… — alayli
– alayli, Commented Jan 14, 2014 at 0:47

Anam · Accepted Answer · 2014-01-14 00:42:52Z

9

Try the following:

Route::get('account', function() {
    if (Session::has('account_id')) {
        $action = 'show';
        return App::make('AccountsController')->$action();  
    }
    else {
        $action = 'index'; 
        return App::make('AccountsController')->$action();
    }
});

Route::post('account', function() {
    if (Input::has('create')) {
        $action = 'create';
        return App::make('AccountsController')->$action();
    }
    else {
        $action = 'login';
        return App::make('AccountsController')->$action();
    }
)};

answered Jan 14, 2014 at 0:42

Anam

12.2k9 gold badges51 silver badges64 bronze badges

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

1 Comment

Anam Over a year ago

The best way to implement this by using filter. i will try to implement an example using filter.

elliotanderson · Accepted Answer · 2014-01-14 00:43:43Z

0

So, you want to put all your logic in the controllers.

You would want to do

Route::get('account', 'AccountsController@someFunction'); 
Route::get('account', 'AccountsController@anotherFunction');

Then, in the respective controllers, you would want to make your tests, then do, for example,

if (Session::has('account_id')){
    return Redirect::action('AccountsController@show');
}
else{
    return Redirect::action('AccountsController@index');
}

However, make sure you define a route for each action, so your application can detect a URL.
For example, if you want to have

 Redirect::action('AccountsController@show')

you will need to define this action like:

Route::get('/account/show', 'AccountsController@show')

answered Jan 14, 2014 at 0:43

elliotanderson

4524 silver badges15 bronze badges

2 Comments

ranieri Over a year ago

Well, as there is no way the user will fall in 2 categories at the same time (if he gets or posts, if he is logged in or not, etc) do I really have to differentiate the actions? I didn't want to have more routes/pages, just /accounts/ for every controller method is enough

elliotanderson Over a year ago

sorry, not sure exactly what you are asking. Technically, you can put the closures in the routes.php file like you were doing before, but the cleanest way to return the redirect action is the way I showed above.

Collectives™ on Stack Overflow

Laravel 4 routing to controller method

2 Answers 2

1 Comment

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related