Plugin activate/deactivate confirmation
2 posts,
3 voices
70 posts
|
Hello, several plugins create an own database table once the plugin is activated and delete it later on once the plugin is deactivated (tidy up). But what if the user just did a mistake? “Just click and the table with all the data is gone.” The feature request: There should be some kind of confirmation mechanism to deactivate the plugin or to deactivate and keep the database table in the backend. This could be achieved by a parameter the settings controller is providing for the “deactivate.php” file. What are your thoughts? |
14 posts
|
I agree, all destructive action should be flagged very loudly as such. |
21 posts
|
I agree. I ran into a problem that the ADMIN section hung up b/c a plugin developer’s website was offline or something, when the admin section looks through the plugins for new update information. My recommendation is the have 2 checkboxes. 1 to install/uninstall (obviously with “are you sure you want to perform this function” text) and the second to enable/disable. In my circumstance I lost all the data because I had to rip out the plugin aggressively to manage my admin section. PLUS, you could debug plugin dependencies later on if you had a troublesome plugin in the future. |