Plugin CRUD

[aydreeihn]

Feature Summary

General CRUD functionality to manage Plugins.

• Delete
• Enable
• Disable
• Update

We will need to determine how/where we will add Plugins in a later project. In the meantime, we can create a dummy Plugin in the database to write the backend to do the remaining functionality.

[DaveWP]

1. As part of this functionality, will it be possible to run named functions within a plugin for CRUD changes?
2. How will this CRUD functionality fit with the existing Plugin Instance CRUD features?
3. Will it be possible to have a plugin with just a single Instance, effectively automatically added when the Plugin is first enabled?

[DaveWP]

Within plugins.php there are several points where an object of class Plugin is called rather than an instance of the actual plugin. Is it possible to call the actual plugin implementation, eg myPlugin. This would provide the capability for plugins to include their own functionality, either before or after the standard functionality by calling the parent equivalent method.

As a use case, I am working on a plugin which will need to create additional database tables so I would want to bind the creation of additional tables on install, and remove the tables when the plugin is "deleted".