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
Let Plugin developers easily store Settings and customize them via UI #4126
Comments
Possibly we add new column in piwik_option table to store plugin, so plugin settings are cleanly separate from core values. |
Would this new mechanism be used to store the phone numbers and validation codes of the MobileMessaging plugin? |
Replying to JulienM:
Nope it would be for pure simple settings label / description / inline help / type / id, to avoid user having to write a controller action+template+form for simple settings. |
…e is no longer a need to use a hook
…o make a plugin developers live as easy and as secure as possible, add automatically validator in case field options are set, for security allow only names that are alNum
…eleted or a plugin installed, needs to be tested
… System setting data objects, the plugin settings does not know anything abotu User/System settings so it is possible to add different kind of settings in the future. Also added nonce when saving settings
…splaying a checkbox, not needed here
…e plugin settings page and explain the user is going to change 3rd party settings
…ins and themes page as well as after activating a plugin
…multi select correct, code cleanup
…ise it is not possible to correct an invalid number
… methods where they belong to not have a circular dependency
… not overwrite each other
Add possibility to define settings for plugins, using radio/checkbox/input/select.
The text was updated successfully, but these errors were encountered: