Changeset 1440622

Timestamp:

06/21/2016 04:43:16 AM (10 years ago)

Author:

RobertGillmer

Message:

Modifications to Readme file

File:

• protect-version-controlled-updates/trunk/readme.txt (modified) (1 diff)

protect-version-controlled-updates/trunk/readme.txt

@@ -12 +12 @@
 == Description ==
 
-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.
+This plugin is built to be used on production servers which are version-controlled with Git or SVN.  If plugins or themes are updated directly on production, they can get out of sync with the repo, and later pushes to the server might "roll back" plugin or theme 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.
+Upon activation, the plugin looks in specific spots for .git or .svn folders and creates settings automatically.  These settings can be modified through this plugin's Settings screen.
+
+Users who try to update a plugin via the Plugins screen or try to update a theme via the Updates 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.
+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.