In the presentation I also gave a demo of the current state of WordPress 2.7 including a live demo of new features like the core updater and plugin installer.

I had been planning for a while to get a slicehost vps server to move all the web properties onto so as to have more bandwidth available for visitors - this site was shifting 5G of traffic a month up my adsl connection on it’s own!

Hopefully all of this site should be running fine now I have got apache2/mysql tuned to run in the limited environment of my 256M slice and wp-super-cache up and running.

Please let me know if anything is broken!

It seems like hardly a week goes by without a new vulnerability in WordPress or one of its many plugins. Many of them are actively being exploited to own popular WordPress blogs and use them to serve spam or client-side exploits to unsuspecting visitors. The popularity of WordPress combined with the abysmal security practices of WordPress plugin developers places the entire Internet at risk and is worthy of a nomination.

To be fair many of the vulnerabities that are reported are within plugin code rather than the core. For more information on the CVEs reported for WordPress and WordPress plugins this year you can head over to the codex.

Here are a number tools that I use most often, these are a set of bash functions which you can stick in your ~/.bashrc file on your linux machine or mac :

//Download a patch from a trac install and apply it to a svn checkout
//e.g. wp-trac-patch http://trac.wordpress.org/attachment/ticket/2345/2345.diff
wp-trac-patch() {
svn revert -R . & curl "$1?format=raw" | patch -p0
}

//Search through a subversion checkout using grep (only search the .php and .js files)
//e.g. wp-grep the_excerpt
wp-grep() {
find . \( -name "*.php" -print , -name "*.js" -print \)  | xargs grep "$1"
}

//Merge a change from trunk to a branch in a subversion checkout of the whole repository
//e.g. wp-merge 1234 2.6
wp-merge() {
svn merge -r $(($1-1)):$1 trunk branches/$2
}

//Output the svn:eol-style property of all the files in a repository
svn-eol() {
find . \( -name "*.php" -print , -name "*.js" -print \)  | xargs svn propget svn:eolstyle
}

I hope you find this useful

]]> http://blog.ftwr.co.uk/archives/2008/03/29/wordpress-25-contributors/feed/ http://blog.ftwr.co.uk/archives/2008/03/29/wordpress-25/ http://blog.ftwr.co.uk/archives/2008/03/29/wordpress-25/#comments Sat, 29 Mar 2008 17:42:20 +0000 westi http://blog.ftwr.co.uk/?p=197 WordPress 2.5 has been released.  Now is the right time to upgrade and give thanks to allow those people that brought it to you. You can read more about it here.

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.

Now to collect the information. First load up firebug for the current page by clicking on the icon in the status bar or using the Tools menu to select “Tools>Firebug>Open Firebug”.

Next you need to fill in the form that is causing you problems:

Now you can click on the form submission button and see the activity in the firebug console:

Next you can switch between the tabs to display the other information:

You can then copy this data out of the firebug windows by right clicking and selecting the appropriate copy option.

This information can then be provided either via the wp-testers mailing list or in the trac ticket you have created for your issue.