WordPress 2.5.1

WordPress 2.5.1 has been released. It includes a number of bug fixes, performance enhancements, and one very important security fix.

If you are interested in only the security fixes, just replaced the following files.

  1. /wp-includes/pluggable.php
  2. /wp-admin/includes/media.php
  3. /wp-admin/media.php

There are more than 70 bugs and performance fixes in 2.5.1, here is an outline of it:

  • Performance improvements for the Dashboard, Write Post, and Edit Comments pages.
  • Better performance for those who have many categories
  • Media Uploader fixes
  • An upgrade to TinyMCE 3.0.7
  • Widget Administration fixes
  • Various usability improvements
  • Layout fixes for IE
1 Star2 Stars3 Stars4 Stars5 Stars (119 votes, average: 3.58 out of 5)

David Potter’s WordPress Plugin Reviews

David Potter has reviewed several WordPress themes and plugins and you can find those reviews here.

He as reviewed 4 of my plugins namely WP-Email, WP-Print, WP-PostViews and WP-DownloadManager.

His reviews are all very detailed, go check them out.

1 Star2 Stars3 Stars4 Stars5 Stars (91 votes, average: 3.58 out of 5)

WordPress 2.3 Released

WordPress 2.3 has been released and I have updated this site to it without any problems.

Copy + Paste from Development Blog

  1. Native tagging support allows you to use tags in addition to categories on your post, if you so choose. We’ve included importers for the Ultimate Tag Warrior, Jerome’s Keywords, Simple Tags, and Bunny’s Technorati Tag plugins so if you’ve already been using a tagging plugin you can bring your data into the new system. The tagging system is also wicked-fast, so your host won’t mind.
  2. Our new update notification lets you know when there is a new release of WordPress or when any of the plugins you use has an update available. It works by sending your blog URL, plugins, and version information to our new api.wordpress.org service which then compares it to the plugin database and tells you what the latest and greatest is you can use.
  3. We’ve cleaned up URLs a bunch in a feature we call canonical URLs which does things like enforce your no-www preference, redirect posts with changed slugs so a link never goes bad, redirect URLs that get cut off in emails on similar to the correct post, and much more. This helps your users, and it also helps your search engine optimization, as search engines like for each page to be available in one canonical location.
  4. Our new pending review feature will be great for multi-author blogs. It allows authors to submit a post for review by an editor or administrator, where before they would just have to save a draft and hope someone noticed it.
  5. There is new advanced WYSIWYG functionality (we call it the kitchen sink button) that allows you to access some features of TinyMCE that were previously hidden.
  6. Full and complete Atom 1.0 support, including the publishing protocol.
  7. We’re using the new jQuery whis is “800% faster.”
  8. Behind the user-facing tags system is a really kickass taxonomy system which, which adds a ton of flexibility. It’s probably the biggest schema upgrade since version 1.5.
  9. The importers have been revamped to be more memory efficient, and you can now add an importer through a plugin.
  10. Through hooks and filters you can now override the update system, the dashboard RSS feeds, the feed parser, and tons more than you could in 2.2.
  11. The new $wpdb->prepare() way of doing SQL queries.
  12. Finally there were over 351 tickets in Trac closed for this release, with over a hundred people contributing. This is the polish, the hundreds of tiny bug fixes and features that make WordPress what it is.

More detailed changes can be found in WordPress Codex.

1 Star2 Stars3 Stars4 Stars5 Stars (43 votes, average: 3.58 out of 5)

DO NOT Use Automatic Plugin Upgrade

I have received several feedback that the Automatic Plugin Upgrade feature in WordPress is causing problem with my plugins.

I want to say that ALL my plugins currently will not work with the Automatic Plugin Upgrade feature because there is a problem with the path. It is a little difficult for me to explain it here.

The new version of my plugins that I am going to release on 1st June 2008 will address this issue. In another words, if are using 1.30 or 2.30 beta of my plugins, the problem has been solved.

So in the mean time, DO NOT use the Automatic Plugin Upgrade feature for my plugin.

Source: WordPress.org Forums: wp-dbmanager is showing as an upgrade for wp-postViews Widget

1 Star2 Stars3 Stars4 Stars5 Stars (127 votes, average: 3.57 out of 5)