Happen to have a WordPress powered site that isn’t hosted on WordPress.com? You’ll want to know about this: The WordPress team has just released version 3.0.2 of the software and it has fixed some nagging issues, as well as one major problem. The full run-down looks like this —
- Fix moderate security issue where a malicious Author-level user could gain further access to the site.
- Remove pingback/trackback blogroll whitelisting feature as it can easily be abused.
- Fix canonical redirection for permalinks containing %category% with nested categories and paging.
- Fix occasional irrelevant error messages on plugin activation.
- Minor XSS fixes in request_filesystem_credentials() and when deleting a plugin.
- Clarify the license in the readme
- Multisite: Fix the delete_user meta capability
- Multisite: Force current_user_can_for_blog() to run map_meta_cap() even for super admins
- Multisite: Fix ms-files.php content type headers when requesting a URL with a query string
- Multisite: Fix the usage of the SUBDOMAIN_INSTALL constant for upgraded WordPress MU installs
We’re big fans of WordPress here at TNW. Since the version 3 release of WordPress, we’re even bigger fans. The MU and WordPress merger had us pretty excited, and the simultaneous plugin updates were just icing on the cake.
If you’ve not tried WordPress before, or if it’s been a while since you’ve given it a swing, it’s time to look again.
This post is part of our contributor series. The views expressed are the author's own and not necessarily shared by TNW.