Craigderroch Castle

This shot was taken in mid October from our living room.
I have been working on a few custom shooting modes on my 30D. One in particular which you’ll be seeing more of is a high contrast / low saturation combination. The reason why I like this combo is because I enjoy the more dramatic shadows, and the contrast boost provides that. The contrast boost also leaves your photo looking a bit too saturated (over-coloured) so to compensate I’ve lowered the saturation at the same time. Sometimes this can make people look really intense, or in weird lighting, dead, but for artistic non-human shots it is working out very well.
The above shot would not look very good in the combo mode. The shot above is based on a lot of similar light, and the obfuscation that it provides. Contrast kills this and many other ambient lighting situations. Anyway enjoy your Friday!

DJ Velvety on Pacific Front Sessions

DJ Velvety
Hey folks, if you enjoyed my November edition of Pacific Front Sessions, I encourage you to check out DJ Velvety’s mix for that same show. The mix is available on the Graham Davis (aka DJ Velvety) website. Great tunes in a smooth mix!
In other news, it looks like I’ll have some more work to do before Flickr and this website play nicely together. It might be a little known fact that Flickr has the ability to post to the newer version of Movable Type blogs. I want to use that ability, but at the same time I like the fact that everything on this website is hosted on this website as well. I am not sure that Flickr would post the image to my archives. There is a feature I would like in the post-to-blog – I would want it to assign the post automagically to a category. This is important because only specific categories will show up on my home page as an update – others are excluded (such as mobile updates) because they are meant for other parts of the site. Entries without a category will not appear at all. So, neato-mosquito, but maybe not yet. Still I like the idea of being able to cross-post across various web-services. Ideally I would like this blog to update my Flickr account to get the photo community benefit. While we’re at it, ideally I’d like my music mix posts to update various relevant forums. That’s gotta be a long ways away, I know, but I am talking in ideals. I want to spend more time making things, and spend less time making the items available in non-invasive ways.

installing movable type 4 on godaddy

I have just updated the site to Movable Type 4 from Movable Type 3.2. Before I get into anything about the new features or new interface, I want to say a thing or two about installation and upgrade.
Six Apart recommends that you make a backup of your Movable Type directory before upgrading. This is a good idea. Do this. They also recommend you overwrite your old installation on the server with the new installation. This is a bad idea. Do not do this. In the event of server incompatibility or an upload error with any one of the hundreds of files required to run Movable Type, your website will be cripled until you can find out what is wrong. Sometimes it can take several days to pin point the problem, which is unacceptable.
This is what I recommend doing:

  1. Make a backup of your database. If you are on a MySQL database, export this and save it to your hard drive.
  2. Make a new database in MySQL. Write down your new database info somewhere.
  3. On the server, duplicate your Movable Type CGI directory, where the application is. This includes mt-config.cgi etc. Name the duplicate directory “mt4” or something to that effect. Keep it in the CGI directory. It belongs there. The new folder should be in a path like “/cgi-bin/mt4/” or “/cgi/mt4/”
  4. Download Movable Type 4.
  5. Uncompress the files. Configure mt-config.cgi to have your new database login info – database user, database password, database name, database server address.
  6. Upload the files to the server, now overwriting the “mt4” copy of your old installation files. If you are on a finicky host like Godaddy, use passive mode in FTP.
  7. Open up the Database backup on your hard drive in a plain text editor and remove the line “CREATE DATABASE [name of your old database];”. Also change the line that says “USE [name of your old database];” and change the name to that of your new database.
  8. In your new database, import the modified database backup. Voila, you now have a copy of your current site’s data that you can use with the new installation.
  9. Set permissions to 755 on all .CGI’s
  10. Go to – it will start upgrading the copy of your database to be compatible with the new bits of Movable Type 4.
  11. Set your password again when upgrading is complete. Re-assign all publishing to a test directory like – if you have special index templates like I do, you will want to redirect the publishing locations to this new test directory. Congratulations, you have a virtual development environment now.
  12. Test your site, including all your plugins. Check out the new nifty plugins area in Preferences. I lost one ( auto-linker) plugin and I had to take code out of my templates. Good to test since this would have caused Movable Type to not be able to build any of my individual entries, of which makes up the majority of my site.
  13. Looking good? Great. Then change the publishing directory back to the main index of the site in preferences. (Just take out “mt4test/”). You are in business now. To be safe, you should remove access to the old Movable Type CGI folder. Rename it or delete it – it is up to you. I renamed mine for backup purposes should anything heinous happen to this installation.

This is a few more steps than what Six Apart suggests, but there are benefits:

  1. You will not be messing with your live site while testing because you have created a testing environment which does not interact with your original installation in any way.
  2. This gives you a chance to iron out the upgrade bugs – and it doesn’t matter what anyone says, there are always upgrade anomalies which you will have to deal with. Plan on it.
  3. The testing environment has all the data, all your templates, but virtually no risk because if there was a problem with an upload or configuration, you can simply reupload without worrying about how long your site will be down for. Your public site wont be down at all.

This is simply making a “development server” out of a testing folder. New set of CGI’s, new database to work with. This is standard practice in any web development environment and can save you a load of worry when doing something as precarious as updating a content management system over FTP. It’s a pretty delicate operation.
One other thing:
Installing Movable Type 4 on a Godaddy server. Ah yes maybe you are looking at this page because you googled that exact term. This is for you then:

#!/usr/bin/perl -w -I/home/content/d/a/v/davinzona/html/cgi/mt4/lib/
$ENV{SCRIPT_NAME} =~ s/-bin\/sbox//;

If you find yourself hosting your Movable Type powered website on a Godaddy server, then you have probably heard that it can’t be done. It’s not true. Change this:
to your username, like:
And put those two lines into all of your .CGI files at the top of each one near the header. Also add it to the file /lib/MT/ inside of your Moveable Type 4 CGI folder.
Okay folks. I can’t sleep tonight because I heard it might snow and I am too excited. This is a lot better than being up because my server is on the fritz. Hope this helps someone. Let me know if it did. Any questions, please leave a comment.