Here is my June 2009 WordPress plugins update containing all my 16 WordPress plugins update. All of them should work on WordPress 2.8 as I did not test them on any WordPress version below that.
Now my plugins uses jQuery for AJAX instead of TW-Sack. I have also updated the widget code to make use of the new WordPress 2.8 new Widget class and that supports multi-instances widgets. The widget code has now been merge with the main plugin file so the standalone widget plugin file is no longer in use. Please delete the whole plugin folder and upload it again to avoid any error.
Here is my December 2008 WordPress plugins update containing all my 15 WordPress plugins update and 1 new WordPress plugin. All of them should work on WordPress 2.7 as I did not test them on any WordPress version below that.
I am introducing a new plugin called WP-CommentNavi which basically paginate your comments similar to how WP-PageNavi paginate your posts. I am also retiring WP-Sticky as WordPress 2.7 has a sticky post feature built in. WP-Sticky 2.31 WILL NOT work on WordPress 2.7 due to a conflict function “is_sticky”. If you renamed that function to “is_sticky2” or something else, it should work, but as usual I did not test it.
Here is my July 2008 WordPress plugins update containing all my 15 WordPress plugins. All of them should work on WordPress 2.5 as well as WordPress 2.6. It is not tested for any version below that.
In general, most of the updates are bug fixes. These updates in theory should be able to work till WordPress 2.7 when it comes out end of this year.
I spoke about Developing Plugins For WordPress on Wednesday, 18th June 2008 at the Singapore PHP User Group, June 2008 meetup.
This is the second time I am speaking at the user group. The first time was in December 2007 meetup where I spoke about the same topic WorPress Plugin Development With PHP.
Here is the second and final wave of my June 2008 plugins update containing the remaining 4 plugins. All of them should work only on WordPress 2.5. It is not tested for any version below that.
The most general noticeable change would be the path to the plugin is now fixed. Previously it was nested in another folder and I got several hate mails because of that. Since the path problem has been solved, the Automatic Plugin Upgrade should work in theory.
Here is the first wave of my June 2008 plugins update containing 11 plugins. The remaining 4 plugins (WP-Ban, WP-DBManager, WP-DownloadManager and WP-PostViews) shall be in wave 2. All of them should work only on WordPress 2.5. It is not tested for any version below that.
The most general noticeable change would be the path to the plugin is now fixed. Previously it was nested in another folder and I got several hate mails because of that. Since the path problem has been solved, the Automatic Plugin Upgrade should work in theory.
As you are might know by now that WordPress 2.5 has been released. Many people have upgrade issues, plugins issues, theme issues, permission issues and what not.
If you are having problem with any of my plugins with WordPress 2.5, check out this 3 links below:
The 2 new plugins are WP-DownloadManager and WP-PluginsUsed. As the name of the plugins suggest, WP-DownloadManager simply enhanced your WordPress by adding a simple download manager to it. WP-PluginsUsed will displays both active and inactive plugins that you are using in your WordPress blog.