Make it possible for users to just overwrite the configuration options that they need to override.

I will make a PR for this

Since this package looks like a perfect pair for anlutro/laravel-settings it would be nice to make them work together.

The issue is that both packages use a common config option: settings.path.
Anluro is providing it as a full path ('path' => storage_path().'/app/settings.json',).
Your package is using just a subfolder path ('path' => 'app/settings.json',).

Since laravel itself resolves paths in config files (eg. cache.php has 'path' => storage_path('framework/cache/data'),) I think this package should have its config changed to reach compatibility.

As a bonus it will make it possible to put config in more places than just storage if needed.

Hi. I've installed this package (config is published and tool registered as said in readme)

Env:
Laravel v6.6.1
Laravel Nova v2.8.0
Package version 1.0 (on the v0.3.3 the same error)

Hey,

Thank you for your package, it's very useful!

I see in your readme that currently there are four available setting types: toggle, text, textarea and code. But a fifth one is mentionned file.

It's currently not working, did you plan to make it works?

Hi @bakerkretzmar ,

Great looking tool, love it! However, the save button in each of my panels is text only i.e not a button nor a link. Any ideas what might be causing this issue?

Cheers,

Package does not seem to be compatible with the lastest version of Nova 4.0.

[2022-04-06 11:10:18] local.ERROR: Class Bakerkretzmar\NovaSettingsTool\SettingsTool contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Laravel\Nova\Tool::menu)

Added fields to nova-settings-tools. Registered with the provider. But in the admin. the panel did not add new fields. What could be the problem? Thank you.

I'm having an issue authorizing the package using the canSee method and a gate.

NovaServiceProvider.php

SettingsTool::make()->canSee(
                function ($request) {
                    return $request->user()->can('permissions.admin');
                }
            ),

The tool is visible in the side menu which would imply that the authorization is working. However once clicked on it gives a 500 error and Call to a member function can() on null is logged meaning $request->user() is returning null.

It seems like something is happening behind the scenes on click which doesn't pass canSee the correct $request? Using the Auth::user() results in the same error. Testing with other packages don't result in the same error.

I really liked your package, but I needed to have the Authenticate::class middleware in the request. Is there any problem to include in Route::middleware?

Nova::router(['nova', Authorize::class], 'settings') ->group(__DIR__ . '/../routes/inertia.php');

Helo I am just install the package. I am doing the required things that is given by you but is shows an error
Class 'Bakerkretzmar\NovaSettingsTool\SettingsTool' not found

Also When I publish there is no nova-settings-tool.php file in config folder. Could not find where the problem is

Any chance to get that? It's complicated? Can I help?

The save button doesn't seem to be getting style appropriately on the latest nova version. I'm on 4.29.5 as you can see in the screenshot

Hi,
When I visit the setting page, it works correctly, but after changing the location to a different resource, it is empty. After refreshing the resource page it is showing.

Nova v4
Opera 86/Firefox 100

Video - https://share.cleanshot.com/lFIu5F

How can i limit access to the Settings to a subgroup of users?

Hello,

Do this module support settings per user?
I mean using some json column settings into user table for example

Regards

Then trying to use field type as textarea the field do not show's up on settings.

[ 'key' => 'message', 'name' => 'Notification message', 'type' => 'textarea', 'description' => 'Popup content.', ],

Hi, how can i get the saved value without making a call to Valuestore, do you have some class or something?

Something like this its what i imaging: NovaSettings::getValue('facebook_url')

Regards

I just faced this issue on the console after installing the package on Nova 4.X.

https://nova.laravel.com/docs/4.0/resources/fields.html#boolean-group-field

There is a need to write to the logs changes that were made to the settings, I would like that when change the settings, event is sent with all the data from the request

P.S. sorry for my English

Thank you for this great package! I would like to translate the frontend strings. Like this:

'settings' => [
        [
            'key'   => 'twitter_url',
            'label' => 'novaSettingsTool.labels.twitter',
            'panel' => 'novaSettingsTool.panels.social',
        ],
]

Then, in resources/lang/vendor/nova-settings-tool/en.json

{
    "novaSettingsTool.panels.social": "Social settings",
    "novaSettingsTool.labels.twitter": "Twitter Profile"
}

Is this possible? Thank you in advance!

Maybe we can add something like the following approach to use saved settings from inside of the app?
I'm using the following code to get settings by their keys with the standard Laravel's config() helper.

app/Providers/AppServiceProvider.php

<?php

namespace App\Providers;

use Cache;

use Illuminate\Support\ServiceProvider;

use Spatie\Valuestore\Valuestore;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        //
    }

    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        // dynamic settings
        $cacheKey = __CLASS__.':'.__FUNCTION__.':dynamicSettings';
        $settings = Cache::remember($cacheKey, 1, function() {
            return Valuestore::make( storage_path(config('settings.path', 'app/settings.json')) )->all();
        });

        foreach ($settings as $key => $value) {
            config(['setting.'.$key => $value]);
        }
    }
}

Hi! I have a problem with styles:

Nova v4.26.5:

Nova v4.22.0:

Hello,

Are you possibly looking into field level permissions? I've narrowed access to by using canSee in the Service Provider level, but there are some fields that I would really not let anyone but the super admin be able to change.

Also, maybe make panels collapsible or be split into sub-pages and show up as sub-menu items in the navigation bar?

Thanks for the great package!
Cheers

Hello,
First, thank you for creating this package!
Is there any simple option to hide it from navigation (not using roles/permissions) ?