Blog entries tagged with "wordpress"

For quite some time my preference has been to wait until the first maintenance release of something before using it. I have found that being an early adopter for something that I just want to use can be extra work, even if it is just having to upgrade again the to maintenance release.

Once I heard that there would be native tag support in WordPress 2.3 I wanted to upgrade to that, but the talk of what would be available in WordPress 2.5 made me want to wait for that. Two weeks ago when 2.5.1 came out I knew it was time to start looking into upgrading.

Last weekend I jumped in and upgraded ride-extravaganza.com, where I am using WordPress as a publishing system, to 2.5.1. This was reasonably straightforward as I, when setting it up at the start of the year, kept my customisations within the theme and plugins. As with all changes I tested it out first on my local server before performing the change on the live sites.

Based on this success I started looking into upgrading this site. Because I was using the now redundant Ultimate Tag Warrior and had made some non standard customisations I expected it to be more work.

And it was.

After some research and experimentation during the week I was ready to upgrade the live site this afternoon. Which, as you are reading this, was successful.

So what did I do?

Which brings us to now and I am happy with the upgrade and can move onto something else in my long list. One of which is running more of this site through WordPress instead of the current mix of WordPress, static files and the custom code for my computer collection.

Ever since I enabled comments I have been using the Akismet Plugin to combat spam which has been remarkably successful:

Today the following comment slipped through:

I was speechless…

After I got my first legitimate comment I started to wonder how they would know if I responded with another comment.

A short time later I found Subscribe to Comments which does exactly what I want. If the commenter checks the notify box they will be emailed whenever there is a followup comment.

As of today is is now possible to leave comments on these posts.

The advantage of using an existing tool for my blog is that all I needed to do to enable comments was to turn on the appropriate option and to copy over (and modify) the appropriate part of the default theme into my custom theme. There was also some effort involved to remove the comment functionality when I first setup the theme but that was a long time ago.

In contrast I would have needed to spend a considerable amount of time building the functionality if I had opted to write everything from scratch. Score one for the first B in bend/buy/build.

(Time will tell if anyone leaves a comment, let alone reads any of these posts…)

Over the past weekend I undertook the next step in rebuilding my linux boxes which was to perform a fresh install and moving services over. As expected installing Ubuntu went smoothly with the first issue arising when setting up the local copy of this site.

Getting apache, php and mysql installed was pretty trivial as I just selected the appropriate packages for installation. After getting used to how the apache configuration files are arranges I quickly had two virtualhosts defined, one for my internal site and another for this site, and I copied the files and databases over.

The snag came when I tried to load up this site and all I got was a blank page. At first all I could find about this issue talked about mysql not loading properly but I knew that wasn’t my issue as the code I had written from scratch that talks to the database was working fine. Eventually I found a reference to the php memory limit. At first I doubled it from 8MB to 16MB. No luck. I tried looking again for other solutions until I thought of doubling it again to 32MB. It was now working.

After a bit of trial an error I found that I needed the memory limit to be at least 26MB for WordPress and the plugins I use to load (but I left the limit at 32MB). Does it use this much memory for every single request and then throw it away at the end? Hmmm…

A few weeks ago I droped the day of the month from the permalink structure of this blog as I realised that I would have to post multiple times every single day for it to be any use.

Although I added a rewrite rule to accomodate the existing links I realised that as the majority of links to my posts were from other posts I had made and those should not depend on the rewrite rule. What I needed was a shortcut in making these links that automatically used the current permalink and also simplify my current process of copying and pasting both the url and title of the relevant post.

A google search later and I had found the Easy Post-to-Post Links WordPress plugin. Unfortunately this created the links with the title of the post, not the contextual form that I use.

After upgrading to the latest version the other day I looked into it again and this time I came across AutoLink which is a much more powerfull plugin that lets me use contextual links as I have been as it picks up a special url scheme.

However when I tried to play around with this one I couldn’t get it running on my local server (I need to update the PHP installation as it does run fine on my paid host) I opted for a compromise which was to adopt the syntax used by AutoLink for post to post links but rewrite the Easy Post-to-Post plugin to do what I want.

One of the many items on my list is to update my local host so that it is running the same versions as my paid host and once I have done that I expect I will give AutoLink another try. My immediate need is to not require the rewrite rule for any internal links.

This evening I upgraded this blog to the latest version of WordPress in under twenty minutes with most of that time waiting for the new files to upload. How did I do it so quickly? By spending over three hours on Tuesday evening upgrading the copy of this site that I run at home and finding the issues there.

As well as upgrading WordPress I also needed to upgrade to the latest version of Ultimate Tag Warrior which has also given me a working tag cloud.

The reasoning behind upgrading was not to upgrade for the sake of it, instead it was the bar that I imposed before moving an a couple of ideas I was considering. Ideally I will look into some of them over the coming weekend.

Many months ago I came across a blog post about how to make wordpress tag based in a similar form to del.icio.us. With my OSDC posts this week I have finally started to add tags and this evening I added in the display of the tags for each post and the display of all the tags in the side navigation bar.

Now I need to find the time (yes, more of it) to go through my past posts and add sensible tags. I shall see how things go…

The new month brings change as this weekend I finally got around to migrating my blog over from my homegrown solution to WordPress as I mused about back in March.

The biggest task involved in the migration was the creation of a theme so the look and feel of the blog could largely remain the same. The biggest change is that there is now a sidebar on all the blog related pages with links to the monthly archives. This has also been the most painful task as although the WordPress templating system may use PHP it does not relate to any half decent programming practives. Each ‘tag’ in the templates is actually a PHP function and some of them print a string, some of them return a string, and some of them have an argument to say whether they print or return. Don’t get me started on everything being global…

At first I thought I would have to write some code from scratch to migrate the existing entries into the WordPress tables but I was pleasantly surprised when I found that WordPress comes with a RSS import script. I did have to modify the RSS generator in my old blog to both include all entries as well as the complete text of each entry but that was fairly trivial which allowed my to discover a bug in the import script. WordPress stores two dates with each entry, the date in GMT/UTC and the date with the desired offset, and in the import script these were back to front which meant that all my posts were imported with a date twenty hours different. This was fairly straightforward to correct and I suppose that I should contribute my changes so no one else has this problem.

The final task involved in the migration was to insert some rewrite rules to redirect requests for my old blog over to the new one. Initially I was going to lookup the old style 12 digit time/date string in the database to determine the exact url to redirect to but I realised that they were wrong anyway because of when I changed back from daylight savings (I’m not going to bother with that in the future) so instead I just extract the date and redirect to the appropriate day archive. The only time this will fall down will be when I posted close to midnight…

My next task (well the next task related to my blog) is to get the trackback functionality up and running and after that are investigations into the numerous plugins that are available…

Due to Good Friday, Easter Monday and Easter Tuesday all being university holidays I am now facing a five day weekend. Although I will end up sleeping or watching movies for most of it I might as well entertain the delusion that I might get something constructive done.

These things may be:

Today I came to the realisation that I am currently afflicted by NIH syndrome with respect to this very blog. Yesterday I was talking about how I was planning to modify this hacked together blog system in order to have more transparent URLs. This is just one of the features that I was planning to add.

For a while I have known about WordPress, an open source PHP and MySQL based blog system, which actually has all the features I was planning. So why should I spend my time writing something from scratch when I could simple take an existing system and adjust it to my needs? Good question…