WordPress released another "urgent security update" a few days ago.
http://wordpress.org/development/2008/02/wordpress-233/
http://wordpress.org/download/

Since I currently run seven different WordPress(.org) blogs, updating can be a time-consuming PITA, so I want to do it quickly and painlessly.
The only file that needs to be updated to fix the security issue is xmlrpc.php ...

However, to make the nag screen go away.....

You need to also update version.php found in the wp-includes folder. For good measure, I updated gettext.php, and pluggable.php as well.

If you don't know what I'm talking about, don't worry.... it's a rather insignificant point in the big scheme of things,
One other thing, if you used the little trick described here to alter your index.php file ... and if you overwrote your existing index.php file when doing a full update, don't forget you will need to edit that header line in the index. php file again, or else you will get this when you try to view your blog:




Hi there,
I knew there were some changes, but that was about it. I cannot imagine keeping up with that many, I have enough trouble with AR & my outside blog.
Cheryl:
Thanks! you saved me lots of time too! I saw today that I need to do another update. I was waiting until the morning to tackle it. Thanks for the timely post!
UPgrade upgrade upgrade...
I found a nice little plug in that makes it all simple
http://techie-buzz.com/wordpress-plugins/wordpress-automatic-upgrade-plugin.html
Enjoy.
Thanks for keeping everyone up on the current info, Cheryl. I just read that Version 2.5 will be due out March 10. For people who pay other people to update their blogs for them, it may be worth it to just update the xmlrpc.php file right now and wait until March 10 to do the full update.
I also read that this update is making podpress act funky, but that's just a matter of changing your settings.