-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared and individual settings #3
Comments
Currently it's possible to add dynamic fields to the database settings (the logged in user's ID, for example - described in the readme) in order to have separate settings. It's also possible to use the |
Okay, I didn't know about One way that came into my mind was defining scopes, instead of extra columns. Although I'm not sure if this wouldn't overcomplicate things.
|
It's a pretty tricky problem... If you use Setting::get you would want to get from both shared and user-specific settings, but if you use Setting::set that should maybe not affect user-specific settings? This may over-complicate things. |
Don't know if I got you right but my idea was basically, that you can set up scopes for different settings. Additionally, you can set up "scopes" (or whatever you want to call them). If you set up the scope called "section1" with
you can write to that configuration file using If you use the default |
Hi anlutro and thank you for this nice package. I wanted to ask if in a future release it could be possible to have shared and individual settings. As far as I see you can only have one of the two at the moment.
With shared I mean settings, that are the same for everyone. If you change the name of the website in a CMS, it gets changed for everyone.
If you change the backend interface language you sometimes don't want other users to be affected.
Is this realizable?
The text was updated successfully, but these errors were encountered: