Plugin settings management (import/export/wipe)

[tott]

Is your enhancement related to a problem? Please describe. When deactivating the plugin a lot of settings are left behind. ie. status of dismissed notices. There is also no way to port settings from one installation to the other which would help for development to production migrations as well as bug reporting and troubleshooting.

I think we need a clear way of identifying the settings that should and that should not be cleared up on deactivation, which settings are publicly shareable and which should be obfuscated and generally provide a more educated interface to maintain settings across features and the main plugin.

Describe the solution you'd like Create a way to register functions that will be executed on plugin activation/deactivation (outside of what we have in features right now)

Creating a settings management class that will replace update_/get_option calls and adding a registration function for settings will give us a more unified approach for controlling settings across features.

Additionally we should extend features to inherit wipe/import/export methods for data stored in custom post types or elsewhere allowing to account for edge cases.

This would allow us to export/import/wipe settings more easily from a centralized place.

[brown-a2]

Hi, has any progress been made on this enhancement? Moving from our dev environment to production, I'd like to be able to export and then re-import our settings.