#2916 closed enhancement (wontfix)
More enhancement to plugin system
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Optimization | Version: | 2.1 |
| Severity: | normal | Keywords: | plugin activation |
| Cc: |
Description
The current plugin system is really good. However, I think that it would be better if we can extend it to require each plugin to define:
1.beforeActivationAction(): do something before activate a plugin, such as altering a table, copying or moving some files...
2.afterDeactivationAction(): return the original status of the system.
Do you think that would be neccessary?
Regards,
Dinh
Change History (2)
Note: See
TracTickets for help on using
tickets.
See: register_activation_hook(), register_deactivation_hook(). They are not required, and should never be, a simple plugin shouldn't have to feature bloat, but they are there for those who need them.