Route to controller in subfolder not working in Laravel 4

Question

I was updating my Laravel 3 app to Laravel 4 when I hit this problem...

Routes I have tried:

Route::get('backend/login', 'backend/UserController@login');
Route::get('backend/login', 'backend.UserController@login');

Answer 1

I had a similar issue just a few hours ago and had to play a little bit with it to have it working.

Routes:

Route::group(array('prefix' => 'admin'), function() {
    Route::resource('/', 'admin\DashboardController');
});

In "controllers/admin" i put the DashboardController:

namespace admin;

use Illuminate\Support\Facades\View;

class DashboardController extends \BaseController {

    public function index()
    {
        return View::make('admin/dashboard');
    }

}

That did the trick on Laravel 4. Hope you find it useful enough. :)

Answer 2

At the moment, in Laravel 4 Beta 1, you can "only ?" use namespace.

For exemple here in your controller file: app/controllers/backend/UserController.php

<?php namespace Controllers\Backend;

use Illuminate\Routing\Controllers\Controller;

class UserController extends Controller {

    // Note extends Controller and not BaseController

    // Your stuff
}
?>

So after, in file: app/routes.php :

<?php
Route::get('backend/login', 'Controllers\Backend\UserController@login');

I don't know if is the better way, but working here. Edit & dump-autoload "composer.json" seems not work actualy.

If someone can improve that, he will make my day ! :)

Answer 3

If you are gonna use Laravel 4, perhaps you should take a look of this: You can specify the namespace to be used on a group of routes, as you can see here: http://www.laravel-tricks.com/tricks/route-group-namespacing

So in your sample:

Route::group(array('prefix' => 'backend', 'namespace' => 'backend'), function()
{

    Route::get('login', 'UserController@login');

});

It works like a charm :)

I've been using it, and are quite good, it helps you keep your code cleaner and more understandable. Give it a try!

Answer 4

I recommend doing

Route::group(array('prefix' => 'backend'), function() {
    // Responds to Request::root() . '/backend/user'
    Route::resource('login', 'UserController');
});

see more info here

Laravel 4 nested resource controllers Route::resource('admin/photo', 'PhotoController'); not working

Answer 5

My Admin Controller in app/controllers directory

class AdminController extends BaseController {
/**.
 * @return \AdminController
 */
    public function __construct()
    {

    }
}

Now I have a folder named admin in controllers folder i.e app/controllers/admin and I have another controller there named AdminDashboardController.php

class AdminDashboardController extends AdminController {

/**
 * Display a listing of the resource.
 *
 * @return Response
 */
    public function getIndex()
    {
    return View::make('admin/dashboard');
    }
    }

And Lastly My Route.php file

Route::group(array('prefix' => 'admin'), function()
{
    # Admin Dashboard
    Route::controller('/', 'AdminDashboardController');
 });

Hope this helps ..:-)

Answer 6

As explained here, with Laravel 4.1 you can specify the namespace to be used on a group of routes, as you can see here: http://www.laravel-tricks.com/tricks/route-group-namespacing

I've been using it, and are quite good, it helps you keep your code cleaner and more understandable. Give it a try!

Answer 7

You could also put your backend/admin panel in a package..fruit for thought :)