Feature #55
plugin_status_model
| Status: | Closed | Start: | 05/19/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 100% |
||
| Category: | - | |||
| Target version: | 0.2.0 | |||
| Resolution: | fixed |
Description
this should work....
each plugin has 1 of 4 statuses:
uninstalled (when a plugin is first dropped into the plugin directory it gets this status)
installed (the install script has run but the plugin is disabled. meaning if the plugin uses DB tables or similar...they have been created but the plugin is still not enabled)
enabled (the plugin has been installed and enabled)
general process (follows #54)
- upload a plugin to the plugins/ directory.
- enable the plugin in the admin panel.
- if the plugin has a status of uninstalled, and it requires an install script to run, it will run now.
- the plugin status will change to enabled.
- disable the plugin
- if the plugin has an uninstall script, the user will be prompted to completely remove the DB tables (or whatever else)
- if the user chooses to completely uninstall, the plugin will change to uninstalled status (start over)
- if the user chooses to keep preferences, the plugin status will go back to installed (but disabled)
History
Updated by Lorenzo Pisani over 2 years ago
1 of 3 statuses sorry =P
so:
- uninstalled (new plugins or purged plugins)
- installed (install script ran but plugin is disabled)
- enabled
Updated by Lorenzo Pisani over 2 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
fixed in 41995170