Well, I’ve upgraded to MT4, and it was relatively painless, once I paid attention to what I was doing. I’ve somehow lost a lot of styling from my arcane crufty old mix of inter-connected stylesheets, all scotch-taped and chewing-gummed together, but everything’s more or less there, so I’ll mark it down as a qualified success. Functional, if not precisely the way I want it to look.

A semi-major style reset is coming soonish, so I’m not going to spend too much time cleaning things up. As wee Derek’s dad used to say in his amusingly authentic Scots brogue: it’ll dooooo, lad.

I’m working on a design update for the old ‘bottle, and I’m going to do it on Movable Type 4, which is now on Release Candidate 4 as I write this, and looking good.

I’ve decided to use XAMPP, an easy-to-install Apache distribution containing MySQL, PHP and Perl, which just works, basically, on Windows, no tweaking necessary (I’m still on XP2 SP2, despite being an early adopter of all Microsoft’s previous OS’s, which is a whole different story.) By exporting the data from this site using the old MT 3.3 export tool, importing it to a local copy of MT running on my machine here at home, I can develop and tweak everything a lot more quickly, and there’s no risk of borking the actual site while I work out the kinks with the new design and the new template structure in MT4, which I’m excited (yes, I’m a geek) to fiddle with.

There are a couple of tutorials out there for getting MT working locally, but none of them actually worked for me by following their instructions, so after hours of fiddling, now that I’ve got it working, I thought I’d share The Secrets. Well secret if the ways of webservers are as arcane to you as they are to me.

The first few steps are easy.

1) Download XAMPP and install it. I installed it to c:\xampp\ to avoid funkiness with long filenames with spaces in them. [Update: word on the streets is that MT will crap itself if you try use to use a path with spaces in it, so c:\Program Files\ is probably a bad idea. Best to stick to c:\xampp\, unless, like me, you're a little compulsive about a clean root directory.]

Choose “No” (you can change this later) when asked to install as a service and “No” when asked to start the Control Panel.

2) Download the PERL 5.8.8-2.2.4 Add-on and install it. (This was the step that was missing from all the other tutorials I saw, and cost me hours of hair-pulling).

Double click the desktop icon and hit the appropriate buttons to start Apache and MySQL. Go to http://localhost in your favorite browser to see if everything’s working. It should be fine. If you see the friendly orange XAMPP home page, you’ve got a working local web server.

2) Download the latest release of Movable Type and unzip it somewhere temporary.

3) Make a folder called ‘mt’ (no quotes) in your c:\xampp\cgi-bin\ folder (if you installed to the same location as I did (I’ll assume henceforward that you did)).

4) Copy all of the Movable Type files (except the folder called ‘mt-static’) to that new location (ie c:\xampp\cgi-bin\mt\). Copy the ‘mt-static’ folder to c:\xampp\htdocs\ instead.

5) Edit the mt-config-original.cgi with Notepad or your favorite text editor. Mine looks like this:

mt-config.cgi

CGIPath    http://localhost/cgi-bin/mt/
StaticWebPath    http://localhost/mt-static
##### MYSQL #####
ObjectDriver DBI::mysql
Database mt
DBUser root
DBPassword
DBHost localhost

I’ve deleted the alternate database lines after what you see here. You can do the same, or comment out the lines with ‘#’. Save the file as mt-config.cgi (omitting the ‘original’ part).

6) Edit all of the rest of the .cgi files (other than the one you just edited) that are sitting in your c:\xampp\cgi-bin\mt\ folder. These are mt.cgi, mt-add-notify.cgi, mt-atom.cgi, mt-check.cgi and so on.

The first lines of each file will read

#!/usr/bin/perl -w

. Change them to (again, if you’re using the same install path as me)

#!C:/xampp/perl/bin/perl -w

in each case and save the files.

7) Go to http://localhost/cgi-bin/mt-check.cgi in your browser. If all is well, it’ll run some tests, and come back to tell you all is well to proceed.

8) Go to http://localhost/cgi-bin/mt.cgi and fill in the forms with a username and password and so on. Note: if the forms are unstyled, you’ll need to check that your path in mt-config.cgi is pointing correctly to your mt-static folder.

9) A few seconds later, you should be up and running in MT4 on your local machine. Yay!

I’m really pleased to see Sixapart‘s new direction with Movable Type. I haven’t really seen that much talk about it around the blogs (which I only keep half an eye on these days, mostly because I’m busy on my own projects and building sites for other people), and I guess that’s an indication of how far the app has fallen in mindshare over the past few years out amongst the blogs.

Of course, there’ve been changes in the weblogging demographics, too, changes that Sixapart decided to chase with Typepad, the Livejournal aquisition, and Vox, possibly to the detriment of MT. The great majority of weblogs these days, I think it would be uncontroversial to say, are run by people who aren’t particularly web-savvy, who don’t care about the technology substrate, who don’t write code and don’t want to, and who are (and this continues to surprise me, because middling as my skills are, I’m in love with design) effectively blind to design. They’re writing their hearts out, or posting pictures of their kitties, or socializing, or trying to build readership and get famous, or just make a buck.

This is in contrast to the first wave of webloggers, who started playing with this stuff from, say, ’98 to around 2001. The tail end of that wave was when I hopped on. Back then, a lot of people were rolling their own content management systems, or (most of them) using Blogger or MT, basically. The relative complexity of MT was no great barrier to a lot of these folks, many of whom were techno-capable (or at least design-oriented) already. That’s changed.

Which is all as it should be, to some extent, perhaps. Since back near the beginnings of the Blog Era, I’ve argued that it’s all about the words. I’m starting to think that that’s less true that I once thought, and wasn’t even as true as I thought it was back when I thought it.

Use your words, stav.

So tools like Blogger continue to present a low barrier to entry, joined by LJ and Typepad and Vox and the very cool Tumblr and hosted WordPress and all the rest, and down in the moshpit, social stuff like MySpace and Facebook. WordPress appears, at least from where I stand, to have emerged triumphant in the host-your-own space, judging only from the enormous number of plugins and themes and tools available out there for it, and the number of high-profile old and new-school personal-website-maintainers that have adopted it.

I’ve tried to like it, but I can’t get my head around the way it cobbles together pages, and I keep coming back to MT.

But I’ve felt in the past few years of the MT Diaspora that I was one of the lonely few, those last couple of people at the party who just won’t go the hell home. I spent a great deal of time learning MT’s ins and outs, learning to love the power of it, and getting pretty handy with it, if I do say so myself. Every time I thought about a new web project (most of which haven’t seen the light of day, of course) that needed some form of structured content, I could always work out a way that MT would handle it. I still love the app, but I started to feel the way that people who never could make the jump from Wordperfect felt way back when, maybe, when it started to become less a de facto standard than a quirky outlier.

I watched Sixapart make all manner of bad and incomprehensible decisions (from the outsider’s perspective, of course). It’s unclear whether the mis-step and ensuing kerfuffle of the new and poorly thought-out licensing policy they introduced a couple of years back was the beginning of the end or the end of the beginning, but things started to seem to go sideways for MT around that time. And even though it turned out that a lot of the pushback and outrage amongst bloggers came as a result of poor corporate communication about the decision rather than the actual licensing changes, it was too late. The water was muddied. Successive revamps of the Movable Type section of the Sixapart site seemed like it was deliberately designed to show off the content-management aspects of MT in the worst possible light, and had to be offputting to anyone thinking of trying the application for the first time. Things became harder to find, the plugin directory was one-dimensionally hard-categorized, tag code examples (if you could find them) dried up and began disappearing entirely, it all seemed complicated and confusing, when the site that showcased the tool should have been showing it off in the best light.

Despite Anil Dash showing up everywhere MT was mentioned, it seemed, sometimes, and being consistently helpful and reasonable (Hi, Anil!), it has seemed for a couple of years that he was the only person left who actually gave a damn about the old-school MT community. I’m sure that impression was far from the truth of the matter, but it was discouraging, despite Anil’s best efforts.

Until recently. Sixapart seems, to me, to be doing almost everything right with the new open-sourcing of a basic version of MT. They’re running the beta wide-open, there’s a nice big download button on the front page of the new movabletype.org website (as opposed to hiding the free version so deep in the last few revs of the .com site that I couldn’t find the damn thing sometimes), they’ve put put up a new MTTags.com site with a whole bunch of reference materials (two tips there — 1) don’t link back to the execrable old movabletype.com reference materials ‘for more information’ please and 2) put a link to the MTTags site in a visible place on the movabletype.org site — I had to search through old posts to find the URL!).

As far as the new application itself goes, well, it’s evolutionary. I’m not overly thrilled or particularly disappointed, but I am happy to see that they’re rethinking some things. The widgets still seem like a half-baked afterthought to me, and the theme management is still opaque to me (which doesn’t matter, because I like to do my own css), but there are some good and interesting ideas there. I’ll continue to use it, of course, unless they break it horribly. But all indications are that they’re listening this time, and taking as much care as they can to make sure we know that.

The most important thing to me, though, is that MT 4.0 is going to have an open-source version, one with no licensing restrictions. I’ll be able to use MT guilt-free to build sites for people, and if they want to buy a license later, that’s up to them, regardless of what they use the site for. That makes me happy, because I still think that of all the tools in the same class that I’ve tried, MT is the one that works for me, and that I feel most comfortable building sites on.

Is it too little, too late? I don’t know. I’m sure there are a lot of other people who’ve hung on, hoping for an MT Renaissance. And I hope that the kind of community that once existed around the tool, all plugins and widgets and themes mutual aid society, like the one that has grown up around WordPress, will grow again. We’ll see.

I’ve spent a lot of words over the years railing against the infiltration of advertising into our weblog world, and enjoyed that righteous glow that comes from standing up for a principle, regardless of how well- (or poorly-) founded the thinking on that principle be.

Here comes the ‘but’.

But I’ve rethought things a bit, in no small part after reading the essay Matt Haughey wrote here.

I’ve always been annoyed by advertising in general, on the web or anywhere else. A lot of my ire in recent years has been directed at Adsense, and that has been mostly because of its ubiquity, I suppose. I’ve always been unshakeable in my conviction that advertising is about the enrichment of the marketing company and the manufacturer of the product or provider of the service being advertised, and about the deliberate manipulation of the people being advertised to, typically to their detriment. Defenders of the Ad often suggest that we, the Consumers, wouldn’t be able to find out about all these products and services created and sold to improve out lives. Well, I suppose there were times when I discovered something I simply couldn’t live without through advertising, but I can’t remember it ever happening. Documentaries like the excellent four part ‘Century of the Self’ did nothing to dissuade me from this, and hammered home for me the ways in which I thought that advertising had interpenetrated and cheapened our modern cultures.

I still think that I’m right about all that.

But Matt triggered some new thinking for me, new thinking that I suppose I’d been tenderized for by building one of my other sites and putting Adsense on it out the gate — the rarely-updated OutsideinKorea. From the get-go, I assumed that it would be a site that people would mostly arrive at from search engines, and not be a regularly-updated, regularly-visited-by-readers webloggy kind of project. And so I put up the ads (for which I’ve still not made enough to get a single check, more than a year later, but I’ve really let it languish, so the fault is nobody’s but my own, from a revenue point of view).

But I hadn’t really followed that thinking through, and what Matt had to say helped me do that.

Two ideas here: that when we’re talking about weblogs and advertising, that an awful lot of people who land on the site (by far the largest ongoing slice of visitors — bar the Digging and Slashdotting et al last year, which was a transient traffic rogue wave) come from search engines. From Google itself, mostly. These people are looking for something, something they’re hoping they might find here. Probably not a product. More likely some piece of information.

It’s possible, I hope, that they find it on the individual archive page they land on here at the ‘bottle, but they might not. If not, then they’ll go on to find it elsewhere, and it’s entirely possible that they might find it following a contextual ad from Adsense.

The ads might actually help them, as well as me, if they click on them. They might actually serve some useful purpose to both parties involved, something I’d never really been able to get behind as a justification for advertisements for the latest variation of Coca Cola, or the newest erectile-dysfunction chemical.

But I didn’t want ads plastered all over the place creating visual clutter for people who actually do regularly visit, who arrive from other weblogs or comments I make elsewhere, or from RSS feedreaders when I make an update. People who are here for the wonderchickeny goodness, not the sifting-through-sum-total-of-human-information.

The solution, of course, as Matt suggested, was to display ads only if people come from one of the traffic firehoses (Digg and Slashdot and Wikipedia and Stumbleupon and the search engines), and not display them if people come from their bookmarks or another weblog or pretty much anywhere else.

I don’t know why I never thought of it before.

So here’s what I’ve done to display ads to visitors conditionally, based on the referrer, using Movable Type. Feel free to borrow and use this yourself — it’s not complicated, and all the reading I’ve done has indicated that it does not in any way violate the Adsense terms of service. There may, of course, be better ways to do it. My coding skills are, to put it kindly, somewhat haphazard.

1) I created a couple of modules in Movable Type, one for each Adsense format I wanted to display. At the moment, I have two modules named module-banner and module-leaderboard Each holds the appropriate Adsense-generated code for that style of ad block, wrapped in a div and a bit of php code to check where the visitor has come from.

The modules look like this. I wrap the whole thing in a div so I can style it, if I want. (You could, of course, customize the referrer list anyway you liked.)

<div class="topbanner">
<?php
if (isset($_SERVER['HTTP_REFERER']) && preg_match("/^https?:\/\/[0-9a-z]*\.?(google|yahoo| stumbleupon|digg| wikipedia|slashdot|lycos|altavista)\..+\/.*$/i", $_SERVER['HTTP_REFERER']))  {
echo <<<END
ADSENSE CODE GOES IN HERE
END;
}
?>
</div>

2) I include the modules in any index template I wish to conditionally display Adsense ads like so:

<$MTInclude module="module-banner"$>

or

<$MTInclude module="module-leaderboard"$>

depending on which of the two ad styles I want to include.

I may make other module variations in future, of course. At the moment, I’m only displaying ads in Individual Archive Templates.

3) I long ago switched all of my extensions over to .php to use some other php inclusions, so that just worked for me. You may need to do make a filetype change (it’s in the settings area in Movable Type) (and possible .htaccess edit — I fly this stuff by the seat of my pants!) .

And that’s it. Now searchers/visitors from the sites I nominate get ads that may help them find what they’re looking for, if it isn’t here, and regular blog visitors who come from pretty much anywhere else don’t. You can test this out by hitting this Google search, then following the first hit back to here. You’ll see ads. Paste the URL directly in to the address bar (for example) and you won’t. Magic!

I probably won’t make much money from this, either. But given the 10,000+ visits that make up an average month at the bottle, more than half of which arrive from search engines, perhaps I’ll make enough for a beer or two each month, and do it without (I hope) annoying any of my loyal readers who’ve stuck with me for all these years.

Share and enjoy.

[Update: Thanks to the most excellent skills of my friends and neighbours, I've made a few changes to smarten up the referrer checking code. Major thanks to Ed Eliot, who was kind enough to whip up something better and explain what the Evil Regex was doing. I've updated the code for the MT modules above accordingly -- my implementation is very slightly different from his, which ought to work anywhere PHP is spoken, of course.]