Fuddland

Entries which have associated advertising provided by Google Adsense.

This category is a subcategory of Indexed.

Here are a couple of small problems I had whilst upgrading to Movable Type 3.3, the solutions of which I’m putting here in case anyone else has similar troubles:

• During the database upgrade process, the error message “Categories must exist in the same blog” means that, for some reason, one of your subcategories has a parent category in a different weblog — the most likely explanation for this is that your database has gotten a bit screwed up. The solution is to either:

  • restore your backed-up database, then use the previous MT installation to change the parent category;

  • edit the database table mt_category directly, using phpMyAdmin or a similar tool if your host provides it.

• If, after rebuilding your weblog, you find that all your weblog entry pages are giving a 500 Internal Server Error message, it may be due to MT setting their permissions to 666. To remedy this, delete all MT-generated content, add the following lines to your mt-config.cgi file and rebuild:

  UploadUmask 0022
UploadPerms 0666
HTMLPerms 0666
HTMLUmask 0022
DirUmask 0022
DBUmask 0022

Today I needed to transfer some of my hard-earned cash to my UK bank account via the Bank of China, so I thought I’d list what information one needs to provide in order to fill out their form, for anyone else who might be searching for help beforehand:

• A photocopy of your passport

• Your bank’s registered address

• Your bank’s SWIFT/BIC [Bank Identifier Code] number [this is a unique code of the form XXXX XX99 assigned to each bank for easy identification], which you write instead of your bank’s usual name on the form

• Your IBAN [International Bank Account Number, which should by EU law appear somewhere on your statement]

Make sure you leave enough money in your pocket to pay the transfer fee — how much you will be charged depends on how much you are transferring, but it can run in a few hundred yuan for transfers of a couple of hundred pounds.

coComment is a new service that allows you to keep track of any comments you make on weblogs; it’s currently in the early stages of development and needs a bit more tweaking to make it work perfectly with the most common browsers and weblogging platforms. Here’s how to automatically allow anyone signed up to its services to keep track of comments they make on MT-based weblogs.

Read the rest of “Integrate coComment with a default Movable Type installation”…

Filed under “I shoulda sorted this out ages ago but it became a priority for me so I finally got around to doing it” was finding an easy way to guarantee that I’m always sending emails over a secure connection, regardless of how I’m connected to the network [whether directly dialled-up to my ISP, plugged in to someone else’s network, or over an unsecure wireless connection].

Perhaps it’s not common knowledge, but generally, when connecting to one’s email service provider using a client such as Thunderbird, Eudora or Outlook, the usual and default set-up is to send the username and password in plain, unencrypted form — anyone listening-in could simply read off your details and have complete access to your account. This is very Not a Good Thing. So the ability to always guarantee a secure connection, at least when sending messages, is quite a handy thing to have.

Why can’t you rely on your own ISP to provide you with a secure connection when sending emails? Most ISPs claim that sending is “secure” because you can only send messages via their [SMTP] servers if you have connected directly to them. But this is no use whatsoever if you’re not dialled-up to them, such as on an unsecure wireless connection, but you still want to send emails.

My solution: use Google’s secure Gmail server. All you need is a Gmail account and to be using an email client capable of establishing secure connections — Opera’s M2 mail offers this facility, as do Thunderbird and Outlook, and probably almost every other modern piece of email software. [It might be called “SSL” or “TLS”, or just a plain old “secure connection” in the settings.]

Read the rest of “Secure sending of emails, wherever you are”…

At some point, presumably around the time Audioscrobbler became one with Last.fm, the format of the RSS feed changed, so it’s time for an updated version of my original feed parser. [Requires a PHP-based site.]

If it’s something you’ll find useful, just:

• install MagpieRSS if you don’t already have it on your server

• download the new version of the script and change the settings at the beginning

See it in action on this very site [of course I’ve added an extra bit to the code which filters out all the Spice Girls tracks I listen to].

Thanks to Robert for making me aware of the change — check out his alternative script if this one doesn’t float your boat.

Prompted by Gordon’s Laziest-of-the-Lazyweb-pleas plea, I’ve made a quick modification to my original Flickr-feed script, so that it now applies various effects [including greyscaling] to the grabbed images. [For example, mine are currently sporting a hint of a bevelled edge.]

You will need:

• The script [rename to flickr.php]

• MagpieRSS

• The GD2+ Thumbnail Class Distro

You’ll also need to ensure you have the GD Graphic Library installed — I’m not sure how you go about checking if it’s there [beyond the script failing]; it appeared to be readily available on my server so I’m assuming it’s fairly common for it to be installed.

See the original entry for more detail.

Read the rest of “Flickr feed parser update”…

Cutting to the chase: I’ve knocked up a PHP script which takes any Flickr photostream RSS or Atom feed and makes a Flickr “badge” out of it, with some extra bits thrown in to make it all worthwhile.

Download the script. Updated version available. Edit it and fill in the required details. Upload it to your server. Cross fingers. [You’ll also need MagpieRSS. Grab it, extract it, stick it somewhere on your server. No need to change any of its settings. Just remember where you put it so you can tell the Flickr script. Oh, and create a writable directory for the cached feed.]

Read the rest of “Use a Flickr feed to include any photostream on your site via PHP and MagpieRSS”…

Although I’d read about it earlier in the month, Lyle reminded me today about Odeon Cinema’s complete lack of understanding regarding accessibility issues when it comes to website design.

The backstory goes like this: Matthew Somerville coded a very nice, accessible portal to the Odeon website, which provided cinema times and the like but without all the unnecessary Flash and other scripty rubbish. He’s done the same with the UK National Rail timetables and a couple of other sites, and they’ve all been lauded for their obvious benefits.

Sadly Odeon’s lawyers didn’t see it that way, and threatened Somerville with legal action unless he took his site down; fair enough he was using copyrighted images, trademarks, etc., but they claimed he was illegally [or, at least, immorally] storing users’ data. Somerville states that he did no such thing and merely passed the data straight on to Odeon’s own database through their usual channels. Nevertheless, Odeon wanted the site down and so it’s gone. I don’t think that’s a particularly clever way to go about their business — or to put it in Lyle’s more apt words, I was keffed off with this bunch of arse — so I dashed off the following email to their contact address.

Read the rest of “Access this, Odeon Cinemas”…

A few weeks back Gordon mentioned a new web-based service called Audioscrobbler, which sounded pretty interesting to me.

Essentially it builds up a profile of your musical tastes — not by asking you questions about which genres or artists you prefer, but by logging exactly what songs you listen to on a day-to-day basis, using a plugin for your media player [a wide range of plugins have been developed]. This information is then compared to other users’, and that’s where the fun begins.

You can quickly find other people who are listening to the same things as you are, and then check out what other artists they also like, building up a network of “friends” whose tastes you respect; you can see which songs by a particular artist are most listened-to, and which users are listening to that artist or song; you can create or join groups dedicated to your favourite performers and join in with discussions about them.

One feature still in development is automatic recommendations — kind of like Amazon Recommendations, but because it would be based on what one actually listens to instead of purchases or on user-entered preferences, it should be more accurate.

They’re also planning to provide a variety of RSS feeds of collective and individuals’ data; currently the only one on offer is for a user’s last ten songs played. Inspired by Richard’s del.ic.ious feed PHP-based integrator, I’ve knocked together some code that produces a nicely marked-up list of the last ten songs in the form of a definition list:

<dl id="audioscrobbler10">
	<dt>Song title</dt>
		<dd>Artist name</dd>
		<dd>[Album title]</dd>
.
.
.
</dl>

You can format this however you like using CSS — for example:

#audioscrobbler10 dl{
border: 2px solid #000;
background-color: #fff;
.
.
.
}

#audiosrobbler10 dl dt, #audiosrobbler10 dl dd{
margin-left: 1em;
.
.
.
}

Read the rest of “Audioscrobbler”…

I’ve long been an admirer of Lump’s commenting system, which allows people to edit their comment for up to 15 minutes after it was originally posted — it allows links that have been messed-up to be corrected or typos to be addressed [some of us could have done with this a couple of weeks ago over at D4D!]. So I was pretty happy when Mark Jaquith guest-posted on Scriptygoddess a technique for MT-based blogs to add this very function.

It took a bit of time to iron out a couple of general bugs, and then some fairly heavy editing of the script to get it outputting things specific to my layout [and to make that output XHTML 1.0 Strict-compliant], but I think it should be working now. I’m not completely sure it will work across all timezones, but time will tell I suppose.

I’ve set the time-limit of the life of the “Edit this comment” link to 20 minutes and the final time-out to be 30 minutes, so if you choose to edit your comment you’ll have a minimum of 10 minutes and maximum of about 30 minutes in which to make your changes, and you can edit it as many times as you like within that time. Note that MT still sends me an email containing the text of the original comment, so if someone drastically changes the sentiment of their comment, I’ll know about it. [Ooh, that sounds a bit like a threat doesn’t it?]

Read the rest of “MTIfNoEntries plugin”…

Read the rest of “This friendly, friendly world”…

Read the rest of “Dynamically-generated MT category archives”…

Read the rest of “YaGoogle!”…

Read the rest of “JavaScript highlighter”…

Read the rest of “Punctuating unordered lists”…