As I mentioned yesterday, I've been having a bit of a spring clean of my website and archiving several areas of content. It took me quite a while to come up with my arching strategy so I thought I'd share what I decided to do.
Outragous I know, but the BBC recently sent me on a training course. No idea why - someone muttered something about "investing in staff" and then ran away. It was a training course in Flash, something the team is increasingly going to be using as it starts appearing in set top boxes and TVs.
One of the legacies of a long lasting site is that you end up moving things around a bit. There are common themes why this can happen - and that means there are sometimes ways to avoid potential problems
Now I must say I do like the visual look and feel of the new BBC homepage, but it gives me yet again, another infuriating problem. It's the browser window size. I just don't want my browser window set that wide.
Of course the sensible thing would have been not to have three different copies of Movable Type for one site in the first place. But then, there's a lot that can be said for hindsight...
Oh poop. It appears that, with the release of Movable Type 4.1, one of the most useful plugins I've ever found for Movable Type - CustomFields - has become part of the MT "Professional Pack", which means buying a licence then. Especially annoying given in its pre-Six Apart ownership, it was essentially donation-ware for personal users.
Two versions of this post. I'll start with the executive summary. If you've moved to Movable Type 4 and find that when you get to edit an entry, the body and Extended fields are all greyed out, then I might have a cure for you!
Over the last few weeks, I've slowly been migrating some of my JavaScript to use the Yahoo! JavaScript event library after discovering that my own attempts at event handling, weren't working quite as well as I'd planned.