Subscribe to
NSLog(); Header Image

MovableType 3.2 Bare Bones Template

Here's a bare-bones template for MovableType 3.2:

Safari renders the page as HTML despite the ".txt," so if you're looking at the template in Safari, have a look at the source. Firefox seems to display the page properly.

4 Responses to "MovableType 3.2 Bare Bones Template"

  1. The .txt extension isn't the important part(which Erik probably knows), it is the "Content-Type: text/plain; charset=UTF-8" header in the HTTP response.

    The argument for doing things the way Safari does is that there are mis-configured servers, so it sniffs and guesses. The downside is that if you need to do what the example URL does, and have a properly configured server, there is no way to convince Safari to do the right thing. I've filed a bug, and I wish others would too. (You can find various rants on the net about content type sniffing considered harmful if you care.)

  2. Indeed, that's an issue. Safari is trying to do the right thing, but when the file extension and the file type/header are in agreement, well…

  3. If you are going to use a "non-standard" extension for your HTML pages, I'd say it is your responsibility to add the appropriate line to the server config to make sure they are served as text/html. If you don't know how, or cannot with the host you are using, changes hosts or use the a standard extension.

    In some (a lot?) of cases, Safari's behavior benefits the user, but in a few cases punishes the user and server admins who set things up correctly - the only workaround in this case is to use a different browser.

  4. I recall reading somewhere (probably from Mark Pilgrim) that Safari has a "feature" where it checks the first 256 bytes of the file, and if it looks like HTML, it's rendered as HTML.