Comments on: My Super Ex-WordPress Official blog of Red Sweater Software Fri, 09 Oct 2015 20:11:22 +0000 hourly 1 By: Simon Wed, 07 Mar 2007 21:34:27 +0000 I use Blogspot. It might not have all the bells and whistles, but I don’t have to worry about installation, migration, security, etc. A few minutes here and a few minutes there, and we’re talking real time!

By: Jeroen Leenarts Wed, 07 Mar 2007 21:30:05 +0000 Yeah he is running an export. Oops :) (I missed the export too)

But then again, do a fresh export, compare that with current running version and the untouched previous version: you’re good to go.

By: Bruno Rodrigues Wed, 07 Mar 2007 20:22:31 +0000 That’s why my comment was related to “my steps”, where I work directly against the WordPress SVN. This allows me to backup my site via storing the svn diffs, and to generate patches to send upstream, when needed.

Or in other words, the changes relative to my personal site should be fully contained inside the wp-content/plugins. If the svn diff command doesn’t return empty, then something wrong is happening on the wordpress codebase – either a bug, or a missing hook in the code.

By: Jose Vazquez Wed, 07 Mar 2007 20:17:15 +0000 Is it my imagination or are most of these comments not noticing that the article did an svn export, not an svn co. if He does an svn update, diff, whatever, it would be working against his local repository of modifications, not against the wordpress repository.
Then again, maybe I’m very wrong.

By: charles Wed, 07 Mar 2007 19:57:59 +0000 Sorry for the duplicate comment above. I should have reloaded the page before posting. And maybe I should not post this excuse? Oh well…

By: charles Wed, 07 Mar 2007 19:56:56 +0000 I believe svn would highlight any difference between your local copy and the remote repository, so you would be aware of removed files when trying to resolve conflicts.

By: Jeroen Leenarts Wed, 07 Mar 2007 18:44:56 +0000 Indeed, when worpress “rm”s a file in the repo it will also go away with an update at your local working copy UNLESS you have local changes. SVN reports this as a conflict and asks you to resolve it.

So your practice is a very nice way to update a wordpress blog. I’m going to look into it as well. Thanks for the tip. :)

By: Bruno Rodrigues Wed, 07 Mar 2007 18:29:45 +0000 If WordPress removes a file, the file dissapears from your local copy. If the file is unchanged, it just goes away. If you did any modifications, there will be a file.php.mine or a file.php.rXXXX.

So, my steps are:
# update local copy with remove files
$ svn up
# check if there’s any conflict…
$ svn status | grep -E “^C ”
# …or just change for the >>>>
$ grep ‘