Warning: cannot yet handle MBCS in html_entity_decode

If you are using PHP 4 and using some of my plugins, the error message “Warning: cannot yet handle MBCS in html_entity_decode” will get displayed on your page. This is not a bug in my plugin but a bug in PHP 4 itself.

My recommendation would definitely be asking you to upgrade to PHP 5. PHP group has announced the end of life for PHP 4 on the 13th July 2007.

Today it is exactly three years ago since PHP 5 has been released. In those three years it has seen many improvements over PHP 4. PHP 5 is fast, stable & production-ready and as PHP 6 is on the way, PHP 4 will be discontinued.

The PHP development team hereby announces that support for PHP 4 will continue until the end of this year only. After 2007-12-31 there will be no more releases of PHP 4.4. We will continue to make critical security fixes available on a case-by-case basis until 2008-08-08. Please use the rest of this year to make your application suitable to run on PHP 5.

As you can see, there would not be any more PHP 4 updates and security fixes will be available till 8th August 2008 which is only 2 more months. If you want to upgrade to PHP 5, this is the best time to do it.

If for some reasons you are not able to upgrade to PHP 5, the only thing you can do is to turn off error message display. You can refer to this thread for more information. This is definitely not an elegant solution.

If you host supports PHP 5 but you are on PHP 4, you can take a look at the solution posted by Thomas Arie Setiawan.

Softwares like MediaWiki which powered Wikipedia requires your server to be running PHP 5, and vBulletin has beginning asking customers to upgrade to PHP 5. It would be a matter of time before WordPress requires a minimum of PHP 5 to be running.

1 Star2 Stars3 Stars4 Stars5 Stars (83 votes, average: 3.60 out of 5)

Lester Chan’s WordPress Plugins June 2008 Update (Wave 2)

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.

Be sure to read the readme.html and checkout the changelog for more information and most importantly NOTE THE TABS AT THE TOP

WP-Ban 1.30
» Readme/Changelog
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-DBManager 2.30
» Readme/Changelog
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-DownloadManager 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-PostViews 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

You may also want to view Lester Chan’s WordPress Plugins June 2008 Update (Wave 1).

1 Star2 Stars3 Stars4 Stars5 Stars (69 votes, average: 3.48 out of 5)

Pre Wave 2

I have completed whatever I need to code for the remaining 4 plugins for Wave 2 release.

WP-Ban and WP-DBManager basically undergo only cosmetic changes to suite WordPress 2.5 layout.

I have added a few minor additions to WP-PostViews. The changes are documented in the Changelog tab in the readme.html file include in the zip

The plugin which undergo the most changes is WP-DownloadManager. It is the longest changelog that I have ever done. I also added a new search feature into WP-DownloadManager. You can see it in action in the Downloads Page.

See Lester Chan’s WordPress Plugins June 2008 Update (Wave 2).

1 Star2 Stars3 Stars4 Stars5 Stars (85 votes, average: 3.68 out of 5)

Lester Chan’s WordPress Plugins June 2008 Update (Wave 1)

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.

Be sure to read the readme.html and checkout the changelog for more information and most importantly NOTE THE TABS AT THE TOP

WP-EMail 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-PageNavi 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-PluginsUsed 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-Polls 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-PostRatings 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-Print 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-RelativeDate 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-ServerInfo 1.30
» Readme/Changelog
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-Sticky 1.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-Stats 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

WP-Useronline 2.30
» Readme/Changelog
» Demo
» Download Mirror #1
» Download Mirror #2
» Support Forum

You may also want to view Lester Chan’s WordPress Plugins June 2008 Update (Wave 2).

1 Star2 Stars3 Stars4 Stars5 Stars (102 votes, average: 3.96 out of 5)