Laravel 4 - Process via controller after validating in routes file - laravel

Question

Im having a little trouble getting used to the whole routes and controllers in Laravel 4.
From my understanding, routes should only be used to decide where to point the URL so it shouldnt be used to process uploads or anything like that.
So basically what i have is my routes file which validates the user fields, then how do i point it to a controller to process teh uploads and everything like that.
I currently have the following code, but when the validation passes and it should go to the controller file, it just displays a blank screen.
Any help would be greatly appreciated.
Route::post('create-profile', function()
{
// Validation rules
$rules = array(
'username' => 'required|unique:users,username|min:4|alpha_dash',
'emailaddress' => 'required|email|unique:users,email',
'country' => 'required',
'state' => 'required',
'genre' => 'required',
'filename' => 'image',
'password' => 'required|min:5|confirmed',
'password_confirmation' => 'required'
);
// Validate the inputs
$v = Validator::make( Input::all(), $rules );
// Was the validation successful?
if ( $v->fails() )
{
// Something went wrong
return Redirect::to('create-profile')->withErrors( $v )->withInput(Input::except('password', 'password_confirmation'));
} else {
// Here is where it seems to all go wrong.
Route::get('create-profile', 'CreateProfileController#processSignup');
}
});

Answer 1

Assuming that your url will be:
http://site.com/create-profile
What I'm showing is not ideal, but I think that your code should look more like the one below:
routes.php
<?php
Route::post('create-profile', 'CreateProfileController#processSignup');
Route::get('create-profile', 'CreateProfileController#signup');
CreateProfileController.php
<?php
Class CreateProfileController extends Controller {
public function processSignup()
{
// Validation rules
$rules = array(
'username' => 'required|unique:users,username|min:4|alpha_dash',
'emailaddress' => 'required|email|unique:users,email',
'country' => 'required',
'state' => 'required',
'genre' => 'required',
'filename' => 'image',
'password' => 'required|min:5|confirmed',
'password_confirmation' => 'required'
);
// Validate the inputs
$v = Validator::make( Input::all(), $rules );
// Was the validation successful?
if ( $v->fails() )
{
// Something went wrong
return Redirect::to('create-profile')->withErrors( $v )->withInput(Input::except('password', 'password_confirmation'));
}
return View::make('success');
}
public function signup()
{
return View::make('signup');
}
}
It's better to have all your routes pointing to controllers actions and let them do the job and, also, it's a little more readable and easy to understand.
Using resource controllers, you can reduce your routes names:
Route::resource('profile', 'ProfileController', array('only' => array('create', 'store')));
Wich will give you those routes:
http://site.com/profile/create
http://site.com/profile/store