Laravel Controller Subfolder routing

LaravelLaravel 4Laravel Routing

Laravel Problem Overview


I'm new to Laravel. To try and keep my app organized I would like to put my controllers into subfolders of the controller folder.

controllers\
---- folder1
---- folder2

I tried to route to a controller, but laravel doesn't find it.

Route::get('/product/dashboard', 'folder1.MakeDashboardController@showDashboard');

What am I doing wrong?

Laravel Solutions


Solution 1 - Laravel

For Laravel 5.3 above:

php artisan make:controller test/TestController

This will create the test folder if it does not exist, then creates TestController inside.

TestController will look like this:

<?php
namespace App\Http\Controllers\test;

use Illuminate\Http\Request;
use App\Http\Controllers\Controller;

class TestController extends Controller
{
    public function getTest()
	{
		return "Yes";
	}
}

You can then register your route this way:

Route::get('/test','test\TestController@getTest');

Solution 2 - Laravel

Add your controllers in your folders:

controllers\
---- folder1
---- folder2

Create your route not specifying the folder:

Route::get('/product/dashboard', 'MakeDashboardController@showDashboard');

Run

composer dump-autoload

And try again

Solution 3 - Laravel

For those using Laravel 5 you need to set the namespace for the controller within the sub-directory (Laravel 5 is still in development and changes are happening daily)

To get a folder structure like:

Http
----Controllers
    ----Admin
            PostsController.php
    PostsController.php

namespace Admin\PostsController.php file like so:

<?php namespace App\Http\Controller\Admin;

use App\Http\Controllers\Controller;

class PostsController extends Controller {

    //business logic here
}

Then your route for this is:

$router->get('/', 'Admin\PostsController@index');

And lastly, don't for get to do either composer or artisan dump

composer dump-autoload

or

php artisan dump

Solution 4 - Laravel

For ** Laravel 5 or Laravel 5.1 LTS both **, if you have multiple Controllers in Admin folder, Route::group will be really helpful for you. For example:

Update: Works with Laravel 5.4

My folder Structure:

Http
----Controllers
    ----Api
          ----V1
                 PostsApiController.php
                 CommentsApiController.php
    PostsController.php

PostAPIController:

<?php namespace App\Http\Controllers\Api\V1;

use App\Http\Requests;
use App\Http\Controllers\Controller;   
use Illuminate\Http\Request;

class PostApiController extends Controller {  
...

In My Route.php, I set namespace group to Api\V1 and overall it looks like:

Route::group(
		[			
			'namespace' => 'Api\V1',
			'prefix' => 'v1',
		], function(){

			Route::get('posts', ['uses'=>'PostsApiController@index']);
			Route::get('posts/{id}', ['uses'=>'PostssAPIController@show']);

	});

For move details to create sub-folder visit this link.

Solution 5 - Laravel

1.create your subfolder just like followings:

app
----controllers
--------admin
--------home

2.configure your code in app/routes.php

<?php
// index
Route::get('/', 'Home\HomeController@index');

// admin/test
Route::group(
    array('prefix' => 'admin'), 
    function() {
        Route::get('test', 'Admin\IndexController@index');
    }
);
?>

3.write sth in app/controllers/admin/IndexController.php, eg:

<?php
namespace Admin;

class IndexController extends \BaseController {

    public function index()
    {
        return "admin.home";
    }
}
?>

4.access your site,eg:localhost/admin/test you'll see "admin.home" on the page

ps: Please ignore my poor English

Solution 6 - Laravel

In Laravel 5.6, assuming the name of your subfolder' is Api:

In your controller, you need these two lines:

namespace App\Http\Controllers\Api;
use App\Http\Controllers\Controller;

And in your route file api.php, you need:

Route::resource('/myapi', 'Api\MyController');

Solution 7 - Laravel

Just found a way how to do it:

Just add the paths to the /app/start/global.php

ClassLoader::addDirectories(array(

	app_path().'/commands',
	app_path().'/controllers',
	app_path().'/controllers/product',
	app_path().'/models',
	app_path().'/database/seeds',

));

Solution 8 - Laravel

php artisan make:controller admin/CategoryController

Here admin is sub directory under app/Http/Controllers and CategoryController is controller you want to create inside directory

Solution 9 - Laravel

I am using Laravel 4.2. Here how I do it:
I have a directory structure like this one:
app
--controllers
----admin
------AdminController.php

After I have created the controller I've put in the composer.json the path to the new admin directory:

"autoload": {
"classmap": [
"app/commands",
"app/controllers",
"app/controllers/admin",
"app/models",
"app/database/migrations",
"app/database/seeds",
"app/tests/TestCase.php"
]
}, 

Next I have run

composer dump-autoload

and then

php artisan dump-autoload

Then in the routes.php I have the controller included like this:

Route::controller('admin', 'AdminController');

And everything works fine.

Solution 10 - Laravel

If you're using Laravel 5.3 or above, there's no need to get into so much of complexity like other answers have said. Just use default artisan command to generate a new controller. For eg, if I want to create a User controller in User folder. I would type

php artisan make:controller User/User

In routes,

Route::get('/dashboard', 'User\User@dashboard');

doing just this would be fine and now on localhost/dashboard is where the page resides.

Hope this helps.

Solution 11 - Laravel

  1. That is how you can make your app organized:

Every route file (web.php, api.php ...) is declared in a map() method, in a file

\app\Providers\RouteServiceProvider.php
 

When you mapping a route file you can set a ->namespace($this->namespace) for it, you will see it there among examples.

It means that you can create more files to make your project more structured!

And set different namespaces for each of them.

But I prefer set empty string for the namespace ""

  1. You can set your controllers to rout in a native php way, see the example:

    Route::resource('/users', UserController::class); Route::get('/agents', [AgentController::class, 'list'])->name('agents.list');

Now you can double click your controller names in your IDE to get there quickly and conveniently.

Solution 12 - Laravel

I think to keep controllers for Admin and Front in separate folders, the namespace will work well.

Please look on the below Laravel directory structure, that works fine for me.

app
--Http
----Controllers
------Admin
--------DashboardController.php
------Front
--------HomeController.php

The routes in "routes/web.php" file would be as below

/* All the Front-end controllers routes will work under Front namespace */

Route::group(['namespace' => 'Front'], function () {
	Route::get('/home', 'HomeController@index');
});

And for Admin section, it will look like

/* All the admin routes will go under Admin namespace */
/* All the admin routes will required authentication, 
   so an middleware auth also applied in admin namespace */

Route::group(['namespace' => 'Admin'], function () {
	Route::group(['middleware' => ['auth']], function() {			 
		Route::get('/', ['as' => 'home', 'uses' => 'DashboardController@index']);				 				  	
    });
});

Hope this helps!!

Solution 13 - Laravel

I had this problem recently with laravel 5.8 but i underestand I should define controller in a right way like this below:

php artisan make:controller SubFolder\MyController  // true

Not like this:

php artisan make:controller SubFolder/MyController  // false

Then you can access the controller in routes/web.php like this:

Route::get('/my', 'SubFolder\MyController@index');

Solution 14 - Laravel

This is for laravel 9.

  1. Organize your controllers in subfolder as you wish:
    controller
    ---folder-1
    ------controllerA
    ------controllerB
    ---folder-2
    ------controllerC
    ------controllerD
  2. use the controllers in the route file
    use App\Http\controllers\folder-1\controllerA;
    .....etc
  3. Write your routes as normal
    Route::get('/xyz', [controllerA::class, 'methodName']);

Solution 15 - Laravel

In my case I had a prefix that had to be added for each route in the group, otherwise response would be that the UserController class was not found.

Route::prefix('/user')->group(function() {
    Route::post('/login', [UserController::class, 'login'])->prefix('/user');
    Route::post('/register', [UserController::class, 'register'])->prefix('/user');
});

Solution 16 - Laravel

Create controller go to cmd and the type php artisan make:controller auth\LoginController

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTinoView Question on Stackoverflow
Solution 1 - LaravelJa22View Answer on Stackoverflow
Solution 2 - LaravelAntonio Carlos RibeiroView Answer on Stackoverflow
Solution 3 - Laraveluser2014679View Answer on Stackoverflow
Solution 4 - LaravelAriful HaqueView Answer on Stackoverflow
Solution 5 - LaravelMervynView Answer on Stackoverflow
Solution 6 - LaravelDevonDahonView Answer on Stackoverflow
Solution 7 - LaravelTinoView Answer on Stackoverflow
Solution 8 - LaravelDipenView Answer on Stackoverflow
Solution 9 - LaravelTodor TodorovView Answer on Stackoverflow
Solution 10 - LaravelKoushik DasView Answer on Stackoverflow
Solution 11 - LaravelYevgeniy AfanasyevView Answer on Stackoverflow
Solution 12 - LaravelMahesh YadavView Answer on Stackoverflow
Solution 13 - LaravelFoadView Answer on Stackoverflow
Solution 14 - LaravelucheNView Answer on Stackoverflow
Solution 15 - LaravelaskepottView Answer on Stackoverflow
Solution 16 - LaravelFarhan KhanView Answer on Stackoverflow