Technology Tales

Episodes of poor performance

Over the last few days, I have been noticing from various that this blog isn't performing as I would want it. The first hint was a comment on a tuxmachines.org mention for a recent entry (thanks for the support, by the way) that the link wasn't working as it should have been. Add to this various emails from Are My Sites Up? saying that the site seemed to be down. By all accounts, this free service that I found through Lifehacker would appear to be doing its job and without the annoying advertising emails that Internetseer used to send me in addition to its weekly report when I used its free service. In fact, that you get alert emails several times a day is a factor in favour of the newcomer.

With one exception, these problems would appear to be intermittent. The exception was when I went using the WP Super Cache WordPress plugin. When it seemed to result in breakage of the site, it got disabled, even if it is meant to be helpful during episodes of heavy load. Otherwise, the outages would seem to be general flakiness of the service provided by my hosting provider. I have a site with them on an older server, and that seems to fare far better than the one playing host to this blog. This sort of thing does make me wonder if we are getting real progress, or whether it's a case of one step forward and two steps back. Nevertheless, I'll continue keeping an eye on things and, if there is too much deterioration, a move might be in order, but that's a good bit away yet.

Remove Revisions 2.2

There is already a post on here devoted to version 1.0 of this plugin, which clearly tells you what it does. The new version will work with the forthcoming WordPress 2.7 (itself a release that's had a development cycle with such upheavals that it would make you want to watch from the relative safety of the sidelines) and has been made to be a little more user-friendly in its actions; in fact, it behaves more like any other plugin now.

Download Remove Revisions 2.2

Dean's FCKEditor for WordPress plugin, a wish list

Admittedly, I have a liking for FCKEditor over and above what comes as standard with WordPress. Here, the FCKEditor for WordPress plugin has been addressing my preference for a while now. However, its most recent release dates from last April and its integration with WordPress 2.6.x has been leaving a lot to be desired. In that vein, I have decided to collect a few of them here:

1. Automatic saves: the idea behind this feature of WordPress is that you aren't hitting the save button that often at all. In fact, given that hitting save creates a revision and an extra record in your database, it really isn't something that you should be doing very often anyway. Unless, you don't mind a bloated database, it's probably best to avoid that habit of saving every few minutes like I do when using Word.
2. Word count: this doesn't update without saving a revision, while it should update periodically in a manner akin to the automatic saves.
3. Insertion of media such as images: this is just broken, and it takes away the possibility of having galleries and captions without manual work.

What I have above are the major inconsistencies, but there have always been annoyances like the adding unwanted   entities allover the place, probably a habit of FCKEditor itself anyway. Nevertheless, it's the integration work that really shows the lack of attention. Maybe, it's time to move Dean Lee's labour of love over to a fully community-maintained course of development. While I know that it's difficult to see your "baby" leave you and take flight, I am inclined that it's the best way forward when you consider how rapidly WordPress has been changing over the last year. Though some moves have been made towards this, they really do need to go further.

A radical new look on the way for WordPress' administration area

One thing that you can never say about Automattic is that it stands still for very long. That may generate adverse commentary from some, yet it's bad to leave things stagnate, too. In fact, resting on laurels also generates flak, so you can't please everyone all the time.

Earlier on this year, the WordPress administration screens went through something of an overall for version 2.5. In hindsight, it wasn't terribly dramatic, but the prospect had me checking out what was happening with the development version and contributing to the project in my own small way. Now, it appears that a bigger upheaval is in prospect with wireframes and what not being brought into play on the design side.

The first change that anyone will notice is that the navigation has moved from the top to the side, and that some things have been moved around and renamed. Another thing that you'll see soon enough is that there is a QuickPress section added to the dashboard screen for those quick and short postings. Sticking with the subject of content creation, alterations to post and page editing screens and the link creation screen are obvious too. The thing that really comes to mind here is the level of customisation on offer, so you can make yourself feel right at home: some of the screen furniture can be moved about, and you can remove what you feel is nothing but useless clutter. Content generates comments, so the addition of keyboard shortcuts for comment moderation should be a boon for those with very active readers.

Some functionality currently added by plugins is getting incorporated in the main application. An example is automatic upgrades of WordPress itself. In the development version, it installs the latest nightly build, but I am certain that it can be made to point to the latest stable release. That makes it more convenient for keeping a backseat eye on things rather than getting stuck into the hurly-burly of checking on what's in Subversion.

There are some pieces that remain incompletely functional at present, such as the Inbox and Media added to this post pieces, but I have seen nothing that used to work to be broken. So, while the development version of WordPress is more of a work in progress than I have seen for a while, it will do what you need it to do. Since you always need to be cautious, I'd advise you to keep away until it's ready for the big time, unless you have the knowledge to put things back should the undesirable befall your blog. I had an automatic WordPress update kick in maintenance mode without turning it off again. Nothing happened to the database, so a manual re-installation was all that was required to restore order. Otherwise, the development installation remains relatively stable, though there are display problems in IE6 that do not afflict either Firefox, Opera or even IE8 Beta2.

All in all, these changes will make the next major WordPress release a substantial one, and I have little doubt that the new administration interface will make for many comments. While I must admit that I wasn't too taken with it when I first glimpsed it in the crazyhorse branch, it now seems to be growing on me. The most significant change on the aesthetic front is that there's a lot less whitespace, about which may or may not float your boat. In any event, you can always change the colours like I have to make things more amenable.

Even so, I reckon that WordPress 2.7 will be a major step forward when it comes, one that I might like. Saying that, I reckon that the release date is a good while away for now, and the fact that 2.6.2 is being readied for release is telling in itself. Leaving plenty of time to remove any roughness is never a bad thing, especially so when you see the changes that are being made. Meanwhile, I am certain that most people can wait.

Another way to look through WordPress code

At times in the past, I have complained about there not being sufficient documentation of the actual code used on WordPress itself. True, there is the venerable Codex, but that can be incomplete, and any extra help is always useful. Peter Westwood (a.k.a. westi) has generated documentation from the code itself and put it up on the web for all to peruse. While we are on the subject of information on the more advanced aspects of WordPress, blogs by Mark Jaquith and Andrew Ozz are also worth a look. As the cliché goes, every little helps...

An alternative use for Woopra

While the once a day reporting cycle of Google Analytics is all very fine, the availability of real time data does have its advantages. WordPress.com's Stats plugin goes some way to serving the need, only for Woopra to trump it in every way apart from a possible overkill in the amount of information that it makes available. The software remains extremely useful despite being in the beta phase and occasionally crashing.

One of its uses is seeing if there are people visiting your website at a time when you might be thinking of making a change like upgrading WordPress. Timing such activities to avoid a clash is a win-win situation: a better experience from your visitors and more reliable updates for you. After all, it's effortless to make a poor impression and an unreliable site will do that faster than anything else, so it's paramount that your visitors do not get on the receiving end of updates, even if they are all for the better.

WordPress plugin for removing post revisions from database

WordPress 2.6 added post revisions as a new feature that is turned on by default. In an earlier post, I described how you could control this by editing wp-config.php and there are a number of plugins that purport to provide the same level of control through the administration screens. Even so, I decided to look at things from the housekeeping side of things and create my own plugin for clearing the database of revisions at one swoop. Currently, it takes out all revisions, but I am thinking of adding the facility for selecting which revision to keep and which to delete. It goes without saying that you should back up your database first in case anything might go wrong.

Download Remove Revisions 1.0

Technical considerations regarding the discussion aspect of blogging

When making a start in the world of blogging, there are so many things to consider that you almost need a trial run first to learn the lingo. In fact, getting up to speed by using a service like that offered by Blogger or WordPress.com seems a very sensible starting point. Even so, the business is like building a house in that you only really know what you are doing after you have done the deed and made all the mistakes. That is particularly true when you go down the self-administered blog route. For starters, it's so easy to pick the wrong domain name or hosting provider. Selecting your blogging software is the next step, but that may not be so tricky; WordPress does a reasonable job and there's always Movable Type, Expression Engine, Drupal (yes, really) or Habari.

That mention of blogging software brings me to something that I encountered recently: commenting functionality. I am coming around to the idea that this is probably something that needs to be considered up front because of the nature of blogging. The Blog Herald's regular readers should understand blogging conversations; consequently, the technology must be easy for visitors to use and simple for bloggers to administer. However, the two can collide. For one thing, there are a myriad of choices available to the blogger, while the blight of comment spam is ever pervasive and growing.

When it comes to comment spam, it is best to realise that there are two sources of responses to a blog post: visitor comments or trackbacks (pingbacks?) from other blogs. As it happens, I reckon that the latter is probably the channel where most of the detritus travels, with various anti-spam solutions are on offer to curb its spread. Names from the WordPress world like Akismet, Spam Karma, Simple TrackBack Validation and Bad Behaviour come to mind. The former can also be used, particularly when the unscrupulous make use of low-cost labour in low-cost countries, and that's when the thorny questions of user registration and CAPTCHA's arise. There is something to be said for not going to extremes with these and just sticking with less onerous rules and filtering on the server side.

Admittedly, I have stumbled into forcing visitors to register before adding a comment and then making them log in thereafter. While I think that it's for security reasons, WordPress creates a password and then sends it to the person who is registering rather than displaying it on a web page. That can create another problem: what happens if the email fails to arrive? In the last week, this has happened with a visitor to my hillwalking blog.

There could be a number of reasons for the non-arrival of the relevant email. One is ironic: being an automated email, it gets stuck in the spam filters of the recipient's mailbox and so never gets to them. It could also be a bug with WordPress itself (I have raised a ticket, and I am awaiting what Automattic might have to say to it) or a consequence of some setting made by a hosting provider. All of that makes it challenging to track down the cause of the issue, yet it kicks off other thoughts as to its resolution. One is to remove the needed for registration and logging in the first place, but there are third-party services that may help too; the former has turned out to be the case for this place. Since it seems to be performing well enough, it is an acceptable option.

When it comes to using third-party comment handling systems, what needs to be considered is how well they work with your blog. For instance, I gave Disqus a quick whirl and soon realised that I needed to update the themes for my WordPress blogs if I were to use it on an ongoing basis. While it worked fine, I was left wondering if it would have been better to have brought it in when I started a blog rather than part way through and with comments made using the existing WordPress functionality. Intense Debate is another option, one of many if my hunch is right. The theme for my hillwalking blog has been modified to allow prospective commenters to get in touch with me if they are having problems. That is only an interim approach while I consider what the way forward will be.

New version of my Countrytones plugin

Now that WordPress 2.6 is out, it is time to introduce a new version of Countrytones to the public. A few CSS tweaks have been needed to the original version after the changes that have been made to the administration interface for 2.6. Those screens still look largely the same with this release as they did before, but for the styling of things like the bubble that alerts you to the availability of plugin upgrades, among other things.

Download Countrytones 1.0.1

WordPress 2.6 out in the wild

Though there was a time when I tested out a new WordPress release when it made its appearance, I now keep tabs on development versions too. It helps me to be ready in ample time and avoid any ugly stuff appearing on either here or my hillwalking blog. On the surface, the changes made don't seem so dramatic after the revamp of the administration interface that came with 2.5. Under the bonnet, many bugs have been fixed, and many behind-the-scenes features have been included for the first time. I'll leave it for you to go to Planet WordPress or check out the relevant entry on the WordPress Development blog. You'll find a Flash video tour of the latest version from Automattic below.

Of course, WordPress development doesn't stop here and there are some considerable changes to the administration interface to come at some point if they ever make out into the mainstream from the crazyhorse branch. I'll be continuing to keep an eye on how things go from here to be ready for whatever might be in the offing. For now, enjoy 2.6, though it'll be interesting to see where it all goes from here.