[Arrow768]

I think it would be a great idea to save the settings in the database (and provide a native in the store plugin to read them)

This would allow to simplify the installation and configuration of the Store Plugin (and its Modules), because there is no need to setup a config file.

The config options could have a attrs tag, where information (like default, min, max value; the type of the input, on-off, text-area, ...) is saved.

The main advantage is the simpler setup of the system, because there is no need to edit multiple config files (because everything can be done via a webinterface)

[alongub]

The advantage of config files over database settings is that you can set different settings per server, which is necessary.

[Impact123]

With the right sheme this is also possible with a database.

Yours sincerely
Impact

[alongub]

Originally Posted by Impact123 With the right sheme this is also possible with a database.

Of course it's possible with a database, but it is much more complex for the user to configure that.

[Arrow768]

Originally Posted by alongub Of course it's possible with a database, but it is much more complex for the user to configure that.

I would not say that.
The following way would be easy for the user:

• The user creates a "settings group" in the webpanel
• This settingsgroup is entered in the config file of the server (its going to be one of the only settings)
• The plugins reads the settings with the correct "settings_group-row"

This way a configuration can be made very easy for the user.
He just needs to create a settings group (that has all the necessary settings for the modules)
And assign a server to the settings group.

I think its much faster this way, because there is no need to log into the server and search for the correct config file and then edit theis file.
The user just needs to go to the webpanel, open the settings group and change the settings

[thetwistedpanda]

It's always safe to assume the end user is an idiot; look at the number of people who can't edit databases.cfg properly. It may be easier in the long run, but likely a nightmare trying to get people set up.

[Arrow768]

Originally Posted by thetwistedpanda It's always safe to assume the end user is an idiot.

You are right, but if there is a good userguide, a lot of the problems can be prevented.

Another option would be to include a default settings group that is accessed by the plugin by default.
So if the user imports the sql dump (as he needs to do it) he has got a working system.

Only if he wants to have different settings for each server he would need to create a additional settings group.
But that can be covered in a guide, so the user only needs to follow the guide (And if the user is not able to read, he would not be able to setup store no matter if the settings are in the db or not)

I know that it is alot of work to implement it but I think there are huge possibilities when the settings are saved in the database.