IT Support Small Medium Business

I just did an in-place upgrade of this site to the latest wordpress 2.3.2 release.

It is neat the update reminder is embeded in admin dashboard.

Since I installed hashcash plugin for this wordpress.org blog site, comment spam has dropped to zero. So, it is effective indeed.

The wordpress hashcash plugin is easy to set up and less intrusive as Capicha! plugins.  However, it seems to be a surge of trackback spams after hashcash plugin choked comment spam inflow. Could it be the spammer actually has logic to detect hashcash plugin in their automation scripts?

I am uite sure the surge is only in eyes of the observer. guess I’d need to bite the bullet and apply for a wordpress.com API key, then enable kismet.

After in-place upgrading this wordpress blog site to the latest 2.3 from 2.2.3 recently, I noticed a problem: auto-save generated an error at the bottom of the WYSIWYG editor window. I said ‘Google search’ turned up nothing, that was true for Google web search and Google group search. When I searchc against blogs, I found some wordpress.org developer discussion about this table being deprecated as of 2.3 release. wonder why auto-save code still uses it. Today, even ‘Google web search’ turned up a few entries. One of them are this deprecated post2cat table caused problem for UFW tag plugin. Read the rest of this entry »

Wordpress 2.3 was out this past Tuesday. I waited two days to be sure no major gotchas in terms of upgrade hurdles as well as security patches. Well, the in-place upgrade went smoothly. However, , I ran into a database problem about a missing table when editing the first new post, aka, this very post, though. Google turned up nothing!

Upgraded the site in-place this morning from wordpress 2.2.3 to wordpress 2.3, to get the following two new features. There are more new features, plus tons of bug fixes. Read the rest of this entry »

Last night, this site upgraded to the latest wordpress 2.2.3 from 2.2.2. Only one security fix was included for this release, to prevent a user from posting arbitrary HTML. Without this fix, “The user only needs to tamper data sent to post.php or page.php and add a field named no_filter with any value”.

Noteworthy on wordpress.org’s site about this release is apparent enhancements on pages of the changed files and bug fixed.  This is nicely done by ‘Trac’, a web-based software project management and bug/issue tracking system.  I never heard of Trac before. will check it out at http://trac.edgewall.org/.

Only the following changed files were replaced in-place for this blog site:

wp-includes/plugin.php
wp-includes/query.php
wp-includes/formatting.php
wp-includes/feed-rss2-comments.php
wp-includes/rewrite.php
wp-includes/version.php
wp-includes/pluggable.php
wp-includes/widgets.php
wp-includes/rss.php
wp-includes/vars.php
xmlrpc.php
wp-mail.php
wp-admin/admin-ajax.php
wp-admin/admin-functions.php
wp-admin/rtl.css
wp-admin/options.php
wp-admin/install-rtl.css
wp-admin/widgets-rtl.css