After a few searches on the wordpress plugin site I found a new comment spam protector and installed that and it was really simple to get it up and running.  Unfortunately for some reason when this was added to the comments forms they were put in an odd place, underneath the submit button.

So the simple install turned into updating all of the themes that I was using to ensure that it was being placed above the submit button.  I also did a quick hack on the php to remove the label that was being displayed.

Wordpress MU

When I was making the move to wordpress mu one of the strangess things that i encountered was a problem with pages and looking at full page articles.  When every I click on the links I would get an 500 internal server error returned.  Since the way that wordpress mu works it has to rewrite the url quite abit to understand what pages to actually get under the covers, for example:

http://phoenix.adamcoulthard.co.uk/blogs/2009/12/08/wordpress-page-hit-internal-server-error

is not an actual page on the server it gets rewritten to something that the server can handle under the covers.  I think alot of the problems were occuring because of the way that I had installed wordpress mu (at least this is what I think).  I had installed wordpress mu into a directory on the webserver rather than putting it into the root directory.  So when it created the .htaccess file with file rewrite information it added a base rewrite of that directory.  So if I installed it into wordpressmu/ then its rewrite base would have been /wordpressmu/ in the htaccess file.

After alot of googling with very little luck and attempting to use the write logging again with no luck, I started to think about what that rewrite base would mean to the system.  So I had a cPanel setup of *.adamcoulthard.co.uk pointing at /html/wordpressmu/ meaning that all the sites had to go to the wordpressmu folder straight away.  So if the rewrite base was adding on /wordpressmu/ then it would mean that it was going to be trying to navigate to /wordpressmu/wordpressmu/…. leading to the internal server error (I would have expected a 404 not found but nevermind).

So what I did was set the base to being just / and that solved the problems of loading the articles.

Wordpress MU

After the upgrade to Wordpress MU for some reason I “lost” all of my images from this blog, oddly the other blog did not have this problem which was very strange!  After abit of digging I noticed that the url’s being returned for the images had /uploads/ in them rather than /files/ I assumed that the old blog was setup slightly different that caused this problem.

The simplest way to fix this was to manually edit all the posts to ensure that they were correct, rather than using the wordpress admin pages I decide to use phpmyadmin again because it was so much easier to edit them all in one go rather than having to navigate pages.

Now all the images are working as I would have expected with is fantastic .

Wordpress MU

As you have probably noticed the site has been bouncing up and down over the last couple of days.  I got an email from my hosting provider to say that I had run out of space on my hosting account.  I had two installs of wordpress on it and wanted to add another but without the space (my hosting provider has upped my limit).

So after abit of searching I tried to use wp-hive which is suppose to be able to use the same installed wordpress code.  I gave it abit of a whirl but at that time it did not provide what I needed, ie the ability to easily move my two old wordpress sites into a central one.  After abit more googling and reading around I thought I should probably try the proper version of wordpress mulit user (WPMU) environment, this runs wordpress.com itself and a number of other high profile blogging sites.

The install of WPMU as for a normal wordpress install was really smooth and worked first time.  I suppose the biggest choice that I had to make when installing was whether to use subdomains or subdirectories.  Initially I thought subdomains so installed it, running through the rest of the install I then hit on whether I could actually update my hosting account to point to the subdomains to the correct location.  So I switched to subdirectories (using a great article).

Using the import I attempted to convert this blog first into the WPMU environment and then switched the subdomain pointer that I already had to point to WPMU.  Sadly this didnt work (still not 100% sure why but I suspect it was something on the URL rewriting), so I had to find a way to do the subdomains with my host.

More googling some time later I found a little trick for cpanel, that in the subdomain pointing its possible to use * as a subdomain and if the host has done the hardwork already in apache (or what ever is being used) all should work.  So I switched WPMU back to being subdomains and setup the blog correctly and everything seemed great!!!

Sadly I hit a few errors as you can probably see if you are reading this in the next day or so all the photos appear to have vanished from the blog! I also hit another couple of problems that I will blog in later blog posts so that they are easier to find for people searching.