Protect Version Controlled Updates

This plugin is built to be used on production servers which are version-controlled with Git. If plugins are updated directly on production, they can get out of sync with the repo, and later pushes to the server might "roll back" plugin updates which weren't committed to the repo. Users who try to update a plugin via the Plugins screen will get a modal window asking for confirmation. Admins can also block updates entirely, so users will still get the modal window but will only have a cancel button. The modal title and modal content are admin-configurable through the options page. Please understand, we're not advocating not updating plugins. You should still update all the things with the quickness. Just do it in the repo and push the changes to the server.

If you're running a version-controlled environment, I'm pretty sure that installing plugins is old hat to you. But just in case...

1. Upload the plugin files to the /wp-content/plugins/plugin-name directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the 'Plugins' screen in WordPress.
3. Use the Settings->PVCU Options screen to configure the plugin.

1.1

• Extensive refactoring of functions to allow for separate choices for plugins, themes, and core (upcoming release).
• Removed the checkbox to disable protection.
• Merged the protection disabling into the radio button choices for plugins and for themes.
• Updated JS to intercept form submissions for updates.

1.0

• Initial release