WordPress 2.0.2 released – Security update

WordPress v2.0.2 has been released with a number of security updates so it is well worth upgrading.

To simplfy the upgrade process I decided to try generating a diff file between 2.0.1 and 2.0.2 and using that to patch my sites rather than uploading a full set of new files.

Here is the process I took on my local machine to generate the diif file:

  1. Exported both 2.0.1 and 2.0.2 from svn using the following commands:

    To get 2.0.2 - svn --force export http://svn.automattic.com/wordpress/branches/2.0
    To get 2.0.1 - svn --force export http://svn.automattic.com/wordpress/tags/2.0.1

  2. Generated a patch file using diff:

    diff -U3 -r 2.0.1 2.0 > 2.0.1.to.2.0.2.patch

I then uploaded the patch file to my server and placed it in my home directory and applied the patch as follows:

  1. Backed up my WordPress database using the wp-db-backup plugin
  2. Made a copy of my WordPress install files as a backup
  3. Then to apply the patch you change into the root folder of your WordPress blog and enter the following patch command:

    patch -p1 < ~/2.0.1.to.2.0.2.patch

And it was done! – There are no database changes between 2.0.1 and 2.0.2 and so upgrade.php does not need to be run as far as I know.

To save you some time if you would like to use this method of upgrade you can download the patch file I generated here: 2.0.1.to.2.0.2.patch.

You use this file with out any guarantee that it will work – Remember to backup first!

5 Responses to “WordPress 2.0.2 released – Security update”

  1. Dickie says:

    Hi Peter, was this written specifically for me, as I now you know I will ask you…!!!!
    Anyway thanks for that
    Dickie

  2. deoren says:

    Neat. From what I can tell rev 3637 of http://svn.automattic.com/wordpress/branches/2.0 is what will be tagged as 2.0.2.

    Also, I’ve read in places that some WordPress users use a working copy of the latest WordPress’s tag or branch. I haven’t found anyone that really had a problem with that. Thoughts?

  3. westi says:

    Dickie: It wasn’t written specifically for you but with you in mind. I had two sites to update quickly and thought that this might be the quickest way.

    Deoren: Yes rev 3637 should get Tagged as 2.0.2 Ryan will probably do that soon he usually does it soon after release. As for running straight off an svn checkout there should be no problems – I have a number of test installs which get updated automatically running the various trunk and branch builds and they work reliably :-)

  4. WordPress News for the week of 3/6/2006…

    With the “hacking” of the original WordPress 2.0 theme competition and a new security release of WordPress 2.0, it has been an exciting week. First a (not so) quick word on the competition then a break down of the changes between .01 and .0…

  5. […] To simplfy the upgrade process I decided again to try generating a diff file between 2.0.3 and 2.0.4 and using that to patch my sites rather than uploading a full set of new files. The process for generating the diff file is actually simpler than the one I used last time! […]



d
go to dashboard
l
go to login
h
show/hide help
e
edit post/page
r
comment on post/page
m
go to moderate comments
esc
cancel
%d bloggers like this: