Comments on: Is WordPress automatic install / upgrade compatible with a SVN deployment of WordPress?

By: Gabriel

Gabriel — Wed, 15 Jun 2011 17:38:57 +0000

@Stephen, yes, WordPress treats plugin upgrades differently. I wish it didn’t but it does. My current method is to keep plugins under version control as well and not upgrade them using the automatic upgrader. A nice improvement would be to change that behavior so that the auto-upgrade process does not delete the .svn directories, but I haven’t looked into what it would take to do that yet. I have tried using the svn:externals method, but I don’t like how it exposes you to buggy plugins — I prefer to download the plugin, test it, then commit it to my svn repository and update the live working copy.

By: Stephen

Stephen — Fri, 10 Jun 2011 22:08:15 +0000

This info might have changed since you last posted — at least for the plugin directory. Check out the following link.

http://nooshu.com/wordpress-plug-ins-and-svnexternals

By: Stephen

Stephen — Fri, 10 Jun 2011 17:00:44 +0000

I upgraded all my Word Press plugins and all of the .svn directories got deleted from the upgraded plugins directories. Very annoying…

By: Gabriel

Gabriel — Wed, 17 Feb 2010 18:51:12 +0000

@estrahon, Lately I’ve been committing everything, but adding a svn:ignore rule for the contents of /wp-content/uploads/ as well as for /wp-content/upgrade/. If you only wanted to keep your theme and plugin directories I’m sure you could do that (since WordPress isn’t deleting the .svn directories) but you’d probably have to check both of them out how you wanted to do so.

By: estrahon

estrahon — Wed, 17 Feb 2010 09:13:20 +0000

Thanks for this! I’ve been looking everywhere for that says these two are compatible and nothing. Even those in the WordPress community believe that you cannot do both.

Do you have the entire WP directory under subversion or is it possible to just commit the theme and plugin directories?