WordPress version 2.3.2 - Major Bug Fixes and New Additions

December 29, 2007, WordPress version 2.3.2 was released to the public, The latest stable release of WordPress (Version 2.3.2)...

Information on the changes and improvements in this new version

The latest WordPress 2.3.2 version fixes a bug that could be used to expose draft posts (http://trac.wordpress.org/ticket/5487
)and information leaks in the XML-RPC and APP implementations. It is recommecded to update to 2.3.2 to protect your blog from these disclosures.

Although it is mainly a bugfix release, it does add a feature which allow you to define a custom DB error page. This would allow your site to fail more gracefully if your database became unavailable for some reason. You simply place your custom template at wp-content/db-error.php. So now, if WordPress ever has a problem connecting to the database, this page will displayed rather than the default error message. Very handy! Version 2.3.2 will also no longer display any database details upon failure as this could be used to aid an attack.


It took me about 5 minutes to create my custom error page, which you can see above, by following these steps:

Creating a Custom WordPress Database Error Page

1. Save the HTML from one of your posts, perhaps by viewing the source of the page in your browser and saving it. Or you can use wget.
2. Edit the saved file to remove extra stuff such as links to previous and next posts, the sidebar, and the comments section.
3. Put the following code where your post’s content would normally go:
error) ) echo $wpdb->error; ?>
4. Rename the file to db-error.php.
5. Upload db-error.php to the /wp-content/ directory.

If you are using WP 2.3.1, Its easy to upgrade, upgrading wordPress from version 2.3.1 should be painless, as there were no changes to the database structure

If you want to make Custom PHP Programming or Word Press Customization, Please contact at http://www.megrisoft.net