Why I got 404 on nova-settings url ?

[sergeynilov]

I have installed outl1ne/nova-settings "^5.2" into Laravel 10 / nova 4.27 app and with default config
file config/nova-settings.php :

<?php

return [

    /**
     * Set a name for the settings table
     */
    'table' => 'nova_settings',

    /**
     * URL path of settings page
     */
    'base_path' => 'nova-settings',

    /**
     * Reload the entire page on save. Useful when updating any Nova UI related settings.
     */
    'reload_page_on_save' => false,

    /**
     * We need to know which eloquent model should be used to retrieve your permissions.
     * Of course, it is often just the default model but you may use whatever you like.
     *
     * The model you want to use as a model needs to extend the original model.
     */
    'models' => [
        'settings' => \Outl1ne\NovaSettings\Models\Settings::class,
    ],

    /**
     * Show the sidebar menu
     */
    'show_in_sidebar' => true
];

In NovaServiceProvider class I defined settings itens as :

    public function boot()
    {
        parent::boot();

//        if ( ! App::isLocal()) {
//            Nova::globalSearchDebounce(2);
//        }



        \Outl1ne\NovaSettings\NovaSettings::addSettingsFields([
            Boolean::make(NovaSettingsParamEnum::USER_ACTIVE_ON_REGISTER->value,
                fn() => $this->resolveUserActiveOnRegisterValue()),
            Text::make(NovaSettingsParamEnum::CONTACT_US_EMAIL->value, fn() => $this->resolveContactUsEmailValue()),
            Number::make(NovaSettingsParamEnum::INVOICE_DAYS_BEFORE_EXPIRE->value,
                fn() => $this->resolveInvoiceDaysBeforeExpireValue()),
        ],
            [
                NovaSettingsParamEnum::USER_ACTIVE_ON_REGISTER->value => 'boolean',
                NovaSettingsParamEnum::CONTACT_US_EMAIL->value => 'string',
                NovaSettingsParamEnum::INVOICE_DAYS_BEFORE_EXPIRE->value => 'integer',
                // ...
            ]
        );
    }

I left 3rd parameter as empty (default 'general' value).

I see new menu item :

https://img001.prntscr.com/file/img001/pNaA_ELwQ-inT8HKEPWgHA.png

but clicking on the menu item I got 404 error and I can not enter settings page.

I run commands :

php artisan route:clear
php artisan config:clear
php artisan cache:clear
php artisan view:clear

The same result.

In php artisan route:list command I see :

  DELETE    nova-api/nova-settings/{path}/field/{fieldName} .......................................................................................................................................................... Outl1ne\NovaSettings › SettingsController@deleteImage

...

GET|HEAD  nova-vendor/nova-settings/settings ........................................................................................................................................................... nova-settings.get › Outl1ne\NovaSettings › SettingsController@get
  POST      nova-vendor/nova-settings/settings ......................................................................................................................................................... nova-settings.save › Outl1ne\NovaSettings › SettingsController@save
...
  GET|HEAD  nova/nova-settings/{pageId?} ................................................................................................................................................................................................................................... 

What did I miss in my settings ?

[Tarpsvo]

Did you add it to the tools?

[sergeynilov]

Yes, and the plugin works ok when I read some parameter from db

[sergeynilov]

I salved this issue after I began using local server with url

php artisan serve

with url for my app

http://127.0.0.1:8000/

Before that I used virtual host of apache 2 under kubuntu 22.04 with php 8.2.

That seems strange for me, but are there some common known errors with virtual host of apache?

[tominal]

I'm getting random 404 errors from these settings pages as well now. Both in production and local. All possible :clear artisan commands have been run..

Edit:
This is so bizarre. I had to define this in my web.php in order to get this working again:

Route::group(['middleware' => ['auth:nova']], function() {
    Route::get('/nova-vendor/nova-settings/settings', '\Outl1ne\NovaSettings\Http\Controllers\SettingsController@get');
    Route::post('/nova-vendor/nova-settings/settings', '\Outl1ne\NovaSettings\Http\Controllers\SettingsController@save');
    Route::delete('/nova-vendor/nova-settings/settings/{path}/field/{fieldName}', '\Outl1ne\NovaSettings\Http\Controllers\SettingsController@deleteImage');
});

I see in route:list there's this line which may be the culprit but I have no clue where it's coming from

[KasparRosin]

The .... on the routes list comes from the fact that we register the callback inside a inline function, which should not be a problem:

            $router
                ->get("{$path}/{pageId?}", fn ($pageId = 'general') => inertia('NovaSettings', ['basePath' => $path, 'pageId' => $pageId]))
                ->middleware(['nova', Authenticate::class])
                ->domain(config('nova.domain', null));

Since you mentioned "random" and "sometimes", I fear the middleware, which checks that the "path" exists, otherwise returns 404, might be the cause somehow.

[KasparRosin]

I can't however wrap my head around how that would be possible since NovaServiceProvider should always run before the middleware and populate the paths/fields.

I'm not running the nova v5 version myself, so if somebody else could share some logs or insights into what is happening inside that middleware, it would be much appreciated 🙏🏻

[JRAscend]

I was also getting a 404 and I found the issue was to do with subpages.

By default, nova-settings expects a subpage named general. If you don't define one, accessing the settings page without a specific subpath will result in a 404 error.

In my case, I was using a custom subpage called opayo. To fix the issue, I had to explicitly append /opayo to the MenuItem path:

protected function bootMenu()
{
    Nova::mainMenu(function (Request $request, Menu $menu) {
        return [
            MenuItem::make('Settings')->path('/nova-settings/opayo'),
        ];
    });
}

protected function configureNovaSettings()
{
    // Define Opayo Settings subpage
    NovaSettings::addSettingsFields([
        // Your fields here...
    ], [], 'opayo');
}

Hope this helps!

[KasparRosin]

Ooh, that would explain why middleware returns 404. Massive insight.

This sort of aligns with my original theory that somehow, something is happening with the $fields array, causing it to be empty. Cause if the fields were not empty, the path created should be fine (as seen on the screenshot).

@JRAscend Could I ask where do you call the configureNovaSettings() function?