Hugh_C's blog about food, photos, music, video editing & other lesser codologies

I’ve come to the conclusion that MovableType is just too hard to work, so I’m moving lock, stock and barrel over to WordPress.  It’s much easier to use. As a result, I’ve separated the site into more sensibly laid out sub domains, the photos are here (photo.intercuts.com), the videos are here (video.intercuts.com) and everything else remains here, where you’re reading this. I’ll try to update the navigation bars in each of the sub domains accordingly.

intercuts

So I’ve just upgraded to Movable Type 3.2 and despite the scary-looking instructions on various websites, it wasn’t too difficult. What was a bit confusing though was backing up the MySQL db, because I’ve absolutely no idea what I’m doing and just follow the instructions blindly. It seems to have been backed up OK.

I’ve been doing some redesign in the category, individual and date archives to make the site a little more easily navigable and more uniform. Not sure it’s too successful yet. It means doing a lot of tweaking in templates files which is pretty hardcore if you’re as ignorant of the goings on in Movable Type as I am.

This is sitting on the 2nd installation of MT, because I managed to screw up the first one by moving the location of some directory or other and stuff got broken. So I decided to go again, except this time I incorporated mysql support, pointing at a mysql database I had set up previously on another server. What I have yet to figure out is where the blog data actually gets stored – is it somewhere on this webserver or is it somewhere in the mysql database itself? Not sure how to determine which of the two.