WordPress 3.3 RC2 has been released.
View: Full Changelog From RC1
Download: WordPress 3.3 RC2
Lester Chan's WordPress Plugins Development Blog
WordPress 3.3 RC2 has been released.
View: Full Changelog From RC1
Download: WordPress 3.3 RC2
The current version of all my plugins will work on WordPress 2.5 PROVIDED you have upgraded your WordPress blog from WP 2.x to WP 2.5.
If you are using a fresh copy of WordPress 2.5 together with my plugins, it WILL NOT work as WordPress 2.5 changes the Activation Global Scope Of The Plugins. In simpler terms, it means that upon activation of my plugins in WP-Admin, it will not create the tables needed by the respective plugins.
To solve this problem temporary, do the following in polls.php (I am using WP-Polls as an example):
Find:
$wpdb->pollsq = $table_prefix.'pollsq';
$wpdb->pollsa = $table_prefix.'pollsa';
$wpdb->pollsip = $table_prefix.'pollsip';
Replace:
global $wpdb;
$wpdb->pollsq = $wpdb->prefix.'pollsq';
$wpdb->pollsa = $wpdb->prefix.'pollsa';
$wpdb->pollsip = $wpdb->prefix.'pollsip';
Note the addition of the “global $wpdb;” and the replacement of “$table_prefix” with “$wpdb->prefix“.
I have updated WP-Polls, WP-ServerInfo, WP-Sticky and WP-UserOnline to work with WordPress 2.5. You can get them here at my downloads page (do note that they are still in beta). Those plugins that end with a “Beta 2” means it will work for WordPress 2.5.
Some of the updates are:
My first plugin to have an uninstaller is WP-Polls and it is contributed by Philippe Corbes. Recently there is a thread in WordPress Forums asking plugin authors to provide uninstaller for their plugins. And that motivated me to add uninstaller to all my plugins, and they will be included in the next release.
I urge all plugin authors to do the same thing to prevent the options table from being overloaded with plugins’ options, and the wost part being that the plugin has already been deactivated and deleted.
“Plugins must call load_plugin_textdomain inside a function that runs on the ‘init’ hook, or at the earliest, the ‘plugins_loaded’ hook.” That is what being stated in Genko Compatibility Page. I have since updated all my plugins to solve that compatibility issue. Hopefully it will not break anything.
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