Straight off from the WordPress.org:
An important security issue has been brought to the attention of the WordPress team and we have worked diligently to bring you a new stable release that addresses it. Our latest version 2.0.2 contains several bugfixes and security fixes.
Today is the first day of March 2006, as usual, I have released updates for 7 of my plugins and created another 3 plugins.
If you are frustrated with my messy installation instructions for my plugins, this update is for you. Now for wp-dbmanager, wp-polls, wp-email you just need to upload the whole folder to the plugins folder, upload the main file to the root WordPress folder and activate and it is done. You no longer need to upload different files to different directories and no longer need to run install/upgrade files.
WordPress 2.01 was released 2 days ago. They had fixed about 114 bugs.
Some of the fixes/improvements:
» You can now specify an upload directory, and whether to use date-based storage or not.
» Caching has been fixed under certain PHP environments.
» Permalinks have been fixed for weird enviroments as well.
» XML-RPC uploading works.
» Compatibility with older versions of PHP.
» Several WYSIWYG fixes and cleanups.
» Imports now use much less memory.
» Now works with MySQL 5.0 in strict mode.
Today is the eve of Chinese New Year, I have release updates for 6 of my plugins. Some of them are just bug fixes. Please check out the changelog for more information.
WordPress 2.0 Plugin: WP-DBManager 2.01
» download
Manages your WordPress database. Allows you to optimize database, backup database, restore database, delete backup database and run selected queries.
WordPress 2.0 is finally announced on WordPress official site. More information about the change in WordPress 2.0.
In the mean time, I have updated ALL my 8 plugins to be compatible with WordPress 2.0.
WordPress 1.5.1 has been released today and here are some of the changes.
» Login and feed fixes for IIS
» Faster gettext i18n
» Improved i18n string coverage
» Extended ping support
» Paging on the Manage->Posts page
» URI-safe accent stripping for all UTF-8 characters in the Latin Extended-A Unicode block
» Query string style argument list support for wp_get_links() and wp_get_linksbyname()
» Improved hierarchy listing in wp_list_pages()
» Support for a Status: theme header field that allows themes to be marked as private, publish, or draft
» Improved caching and database query reduction
» Active plugin and theme highlighting
» Plugins can now have multiple option pages
» Pingbacks now work on hosts with fopen off like Dreamhost
» Many bug fixes
As the title of this post says, I have updated this site to WordPress 1.5. It is the smoothest upgrade I have ever been through. No errors or major mishaps at all, just some very minor cosmetic bugs. If you found any errors, please drop me an email or post it in the forum. I have made a habit of reading my forums once every 2 days =)
I have updated all my WordPress Plugins to be compatible with WordPress 1.5. However, this site is still running on WordPress 1.2. I will upgrade it as soon as I modified the templates. Apparently modifying codes is much more interesting than modify codes. LOL.
My Plugins For WordPress
» WordPress 1.5 Stats – download
Display your WordPress statistics.
WordPress 1.5 had been released a few days back, it is quite a major release comparing it with 1.0->1.2. This site runs on WordPress 1.2 and I will definitely upgrade it to 1.5 if I have the time to hack all my plugins to 1.5 compatible and the problem is that there are quite alot of them.
Spend a few hours yesterday upgrading this site on my localhost to WordPress 1.2. Customised all the hacks I did for my WordPress to make it compatible with WordPress 1.2. It is kinda easy, the API didn’t change much. I love the new plugin architecture. Just drop it in the plugin directory, activate it and you can use the function. It is much neater than my-hacks.php.
Once I am satisfied with the site on my localhost, I just upload it to the live server and it is done. I always like to do stuffs on my localhost first.
