Now WordPress 2.5 RC1 is out it the wild for testing we are receiving some reports of strange problems with some of the ajax functionality in the admin pages so I have prepared a quick tutorial to help people collect the relevant debugging information to help us investigate the problems.

Here is how to prepare:

1. Install Firefox (if you don’t have it already!)
2. Install firebug. This is the web debugging tool of choice.
3. Load up the relevant WordPress admin page that is not working for you.

(Read on …)

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:
(Read on …)

In preparation for the first WordPress Bug Hunt this weekend Mark Jaquith has written some excellent instructions on how he “does work” on WordPress on Linux / Mac OS X.

Skippy who is one of the hosts of the bug hunt was looking for a Windows version of Mark’s cheat sheet - So here or those of you using Windows the following instructions show you how to achieve the same things.

First of all you need to install an svn client, the svn client of choice on Windows has to be TortoiseSVN which is not only a subversion client but also includes patch application functionality and visual merge tools. Once you have installed TortoiseSVN you will now be set and ready. So here is the “Working on Windows” version on Mark’s instructions:
(Read on …)