Suggested download: Google Myth Exposed! Don't fool yourself!
Powered by MaxBlogPress  

 

WordPress 2.3.2 Released!

WordPress 2.3.2 Released!

Jan 2008 | Category: News and Rumors

taken from the original source

Newly released WordPress 2.3.2 has an urgent security release that fixes a bug that can be used to expose your draft posts. WP 2.3.2 also suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations. Get 2.3.2 now to protect your blog from these disclosures.

As a little bonus, 2.3.2 allows you to define a custom DB error page. Place your custom template at wp-content/db-error.php. If WP has a problem connecting to your database, this page will displayed rather than the default error message.

For more detail on what’s new in 2.3.2, view the list of fixed bugs and see the changes between 2.3.1 and 2.3.2.

Special thanks to Alex Concha for his help on this release.

Technorati Tags: ,,

If you like this post, why not subscribe


More articles you'll like:


Fast and semi auto bookmark to 45 social bookmarking services! Add to Technorati Favorites Add to Mixx! Add to BlogEngage



Blog Responses to this post:

2 Comments | Subscribe to Comments by Email or RSS | Trackback URI »

rhyan on 2008-01-08 00:31:04 said
MyAvatars 0.2

it’s so funny, I haven’t tried to update my WP yet. can’t find an easy tips to update any idea?

 
Louis Liem on 2008-01-10 19:37:55 said
MyAvatars 0.2

same here. mine is still 2.3.1. i’ve implemented the update on my localhost and there’s no problem.
it’s very simple to update. all you need to do is overwrite the old files. that’s all.
however, there’s a WP auto update plug-in available if you want to try.

 
Author / Blog Name
E-mail (optional)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.
Subscribe to comments via email

« Previous Post     Next Post »