I’ve updated my Autolink Drupal module to version 1.3.

The only change with this version is that it now works properly with Drupal 4.6. See the Autolink project page for more details.

Following my site being hacked, I’ve finally been spurred into updating to the latest version of Drupal. Please let me know if you spot any problems.

I suspect that the reason that I was hacked was that I was still running a version of 4.5 which had a security hole in it. This in turn was because I had been putting off the upgrade as it wasn’t reversible and looked like it might require performing some SQL updates. I think that the difficulty of installing and upgrading Drupal are one of its major weaknesses. It often involves backing up, manually downloading items, running scripts, issuing SQL commands, moving files around, all of which can be quite daunting. I’m very capable of doing such things, but the more steps there are, the more it looks like something might go wrong - so you start thinking that you will have to have enough time available to recover from any catastrophic cock-ups, and hence you put it off for another day…

It should be possible to automate most if not all of this process. Installation really ought to be a case of clicking one icon or running one shell script. Creation of databases could and should be automatic, or performed in a wizard on the actual site that it being installed.

New versions of Drupal ought to be detected automatically, and there ought to be an option on the admin page of a site to allow you to perform an update. This update should be performed safely - making a complete backup of all data first - without the administrator having to perform a backup themselves.

Installing updates and custom modules ought to be possible from within Drupal itself, in the same way that Eclipse - for example - has a built in update mechanism. The admin page ought to display a list of all of the items that are available on drupal.org, and there should be support for downloading and installing them from within Drupal. When a new module is enabled, it ought to perform any SQL creation/updating that it needs to do, without the user having to do anything themselves.

All of this wouldn’t be rocket science - the technology mostly exists already, it’s just a question of people taking the time to package things up nicely.

I’ve updated my Autolink Drupal module to version 1.2.

New with this version is the ability to add text which will be inserted into a rel=”” attribute on the automatically generated link.

You can use this to insert anything relevant into the rel attribute, for example you could use it to add XFN information to links.

Looking at my logs, I noticed that I was getting quite a lot of people looking for old links, particularly for Last Exit to Hypercard.

As a result, I’ve put up most of my old site at http://old.elegantchaos.com.

I’ve updated my Drupal module Autolink to version 1.1.

To use Autolink, you define a Drupal taxonomy and add some terms to it.

When any of these terms occurs in text on your site, Autolink automatically adds an html link to whatever URL you have specified for that term. So, for example, you can enter terms for all of your friends, then any time you refer to them in a post, their names will automatically be linked to their blogs.

The main change in this version is that you can specify some replacement text, so that when the link gets created, the replacement text is displayed instead of the original text.

As an example of why replacement text is useful, say we defined a term “Apple”, to be linked to “http://www.apple.com”. The danger with this is that an article containing the word “Apple” in another context might inappropriately be linked to the Apple website. We could use a less ambiguous term, like “Apple Computer Inc.”, but we don’t want that text to have to actually appear in all of our articles, because it is unnecessarily formal. The solution is do match for “Apple Computer Inc.” in the article, but provide a replacement that converts it to “Apple” in the final output. Now it’s unlikely to be matched incorrectly, but the text will still read ok.

For more details, see the Autolink project page.