Route Group Returning 404 Not Found for Index Method

@Talinon Thank you for taking a look at my issue. I don't have a constructor declared in the OwnerController and the controller itself simply extends the base Laravel Controller class. I also haven't added anything to the RouteServiceProvider. It has the content Laravel generates by default.

class RouteServiceProvider extends ServiceProvider
{
    /**
     * The path to your application's "home" route.
     *
     * Typically, users are redirected here after authentication.
     *
     * @var string
     */
    public const HOME = '/dashboard';

    /**
     * Define your route model bindings, pattern filters, and other route configuration.
     */
    public function boot(): void
    {
        RateLimiter::for('api', function (Request $request) {
            return Limit::perMinute(60)->by($request->user()?->id ?: $request->ip());
        });

        $this->routes(function () {
            Route::middleware('api')
                ->prefix('api')
                ->group(base_path('routes/api.php'));

            Route::middleware('web')
                ->group(base_path('routes/web.php'));
        });
    }
}

@steel82 Have you added anything to your web middleware group in /app/Http/Kernel.php? (or try temporarily removing the web middleware from the Route Service Provider just to test)

@Talinon I haven't added anything to the web middleware group in the Kernel. Here is the key value for what it has loaded out of the box:

protected $middlewareGroups = [
        'web' => [
            \App\Http\Middleware\EncryptCookies::class,
            \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
            \Illuminate\Session\Middleware\StartSession::class,
            \Illuminate\View\Middleware\ShareErrorsFromSession::class,
            \App\Http\Middleware\VerifyCsrfToken::class,
            \Illuminate\Routing\Middleware\SubstituteBindings::class,
        ],

I just attempted commenting out the web middleware from the Route Service Provider and ran php artisan route:list. It showed all created routes were removed and displayed the api routes laravel ships with.

Speaking of, I haven't mentioned it, but I am using Laravel Version 10.

I restored the web middleware routes in the Route Service Provider and rechecked php artisan route:list. All of the routes were back. Attempting to access the page still returns a 404 Not Found unfortunately. Great suggestion though!

@Snapey Apologies, the URL that I'm attempting to access is http:\\localhost\businesses\owners

@steel82

did you run this without artisan serve, or you already aliased your virtual host.

is it work if using this url ?

http:\\localhost\your_app_name\businesses\owners

or

http:\\localhost\your_app_name\public\businesses\owners

@steel82 and your working edit route is in the same format (in the URL)

@tangtang I'm not using artisan serve . I'm using a Virtual Host set up in apache.

Here is a small correction to the URL. http:\\llama.test\businesses\owners This has the same results.

Here is the configuration file for the Virtual Host.

<VirtualHost 127.0.0.1:80>

        ServerAdmin webmaster@localhost
        ServerName llama.test
        ServerAlias www.llama.test
        DocumentRoot /var/www/llama/public

        #SSLEngine on
        #SSLCertificateFile /etc/pki/tls/certs/llama.test.crt
        #SSLCertificateKeyFile /etc/pki/tls/certs/llama.test.key

        ErrorLog ${APACHE_LOG_DIR}/llama.error.log
        CustomLog ${APACHE_LOG_DIR}/llama.access.log combined

        <Directory /var/www/llama/public>
                Options Indexes FollowSymLinks
                AllowOverride All
                Require all granted
        </Directory>

</VirtualHost>

My hosts file ties the llama.test to the localhost IP. Here is the hosts file contents:

127.0.0.1       localhost
127.0.0.1       llama.test
::1             localhost
127.0.1.1       pop-os.localdomain      pop-os

@Snapey The edit route works. Here is the URL accessed when hitting the edit function: http://llama.test/businesses/owners/edit/2

or

http://localhost/businesses/owners/edit/2

Either works.

@steel82

may be this .htaccess is missing in public directory. if it's missing or not configured correctly, it can lead to 404 errors

@Talinon Great idea! It still returns the 404 Not Found :(

Do you think it could be something going on with the .htaccess file in the public directory?

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Send Requests To Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

@steel82 do you get the same results with businesses/owners and businesses/owners/

@steel82 Yes, I'm starting to think it's webserver configuration.

Try this on your webserver config for the vhost:

               <IfModule mod_rewrite.c>
                        Options -MultiViews
                        RewriteEngine On
                        RewriteCond %{REQUEST_FILENAME} !-f
                        RewriteRule ^ index.php [L]
               </IfModule>

@steel82 in your virtual host config, try

        <Directory /var/www/llama/public>
                Options -Indexes FollowSymLinks
                AllowOverride All
                Require all granted
        </Directory>

changing Indexes to -Indexes

then reload apache

@Snapey I tried adding the '-' in front of the Indexes. Apache complains that I need to precede all options with either '+' or '-' or nothing. I tried both. Options -Indexes -FollowSymLinks serves a 403 Forbidden to all pages. Options +Indexes +FollowSymLinks results in serving the pages, but still have the 404 issue.

I think I've narrowed things down to an issue with how I'm defining my routes for my BusinessController. I'm going to attempt to explicitly define them as opposed to using Route::resource on them to see if that solves the issue.

@steel82 in which case, should have been

Options -Indexes +FollowSymLinks

@steel82

resource route for 'businesses' is interfering with the routes for 'businesses/owners'. when you define a resource route, it automatically generates routes for various CRUD operations (create, read, update, delete) related to the 'businesses' resource. In your case, it's causing a conflict because 'businesses/owners' is also a route that you want to define explicitly.

maybe nested route group can help

Route::resource('businesses', BusinessController::class)->middleware(['auth', 'verified']);

Route::prefix('businesses')->group(function () {
    Route::resource('owners', OwnerController::class);
});

@steel82 Say again, routing to controllers has F'all to do with views and folder structure.

@steel82

The explanation by @tangtang is solid. You'll find that you're hitting the BusinessController methods instead of OwnerController.

@Talinon 100% agree. I marked the answer he gave as the solution. It was indeed a collision.

@steel82 You can reorder the routes so that businesses/owners (etc) is matched before businesses/foobar/

Then both can co-exist

Alternatively rename one eg business/{business}

Problems like this always take longer to spot when you only have a small fraction of the picture

@Snapey Great advice. I'll try moving the Owner Routes ahead of the Business Routes to hit them first.

@Snapey That worked like a charm. That'll save me from reworking my file structure and keep the views nice and tidy. Thank you!

@steel82 once again....... its got nothing to do with the views or the file structure thereof.