Movable Type Update

I updated to Movable Type 3.2 today. Not any big differences that I can see, although it will allow me to customize more of the pages without having to hack the perl code underneath. I still have to move this all on to the big server (Nova) at a real collocation facility.

Posted on October 5, 2005 9:32 PM


Comments

Testing TypeKey Authentication

So what the hell is an "OpenID URL?"

I see your gravatar just fine though. That leering fish!

Also saw the comments you and that other fellow left about my gaming dice post. Yeah. I agree straight edges and sharp corners will wear faster unless your playing on a nice padded surface. Casinos don't have to worry about this since they wear out and replace craps dice very rapidly of the course of a year. Gamers, being habitual cheapskates, might not go for that. I viewed the whole idea as a gimmick anyway. Actually Gamescience has made straight edged, transparent polyhedral dice for many years now.

And in the case of plastic with different density yet the same transparency and refraction index, well that's when you drop the thing in water to see if it favors any faces. The casino's thinking is that transparency makes it at least slightly harder load dice and easier to spot bubbles.

You'll be happy to know that I just migrated to GAIM. As a side task, I also set my password to be the same on all services. I got tired of remembering different passwords for each.

So I don't know when I'm going to upgrade to MT 3.2 myself. I've still got a list of things I want to set in my current version

I suppose if I were really serious about making MT my total site CMS solution, I'd demand that you give me control of .htaccess so I can put in redirects for all my old page locations.

I'm not really needful of that though so, GM stays in place, all the old pages stay in place and Google remains as my site specific search tool, not MT.

OpenID is a federated identification service that allows you to create a trust relationship to a website. The idea in a nutshell is that you prove who you are via ownership of a domain. I obviously own bakafish.com so I can use that to verify to another site that the owner of bakafish.com is the one who is posting. MT has client and server plug in's that allow you to use it as an alternative to their own TypeKey system, which has a similar function, but is dependent on a centralized server.

I still insist that you could have imported or configured MT to deal with your old content transparently without stupid redirects or changing the previous URL's. It generates content out of a small straightforward DB and it would have been simple to get it aligned with what was there before. Doing redirects to static content seems totally dumb.

Yes, I could have I suppose but it wouldn't have been easy and it wouldn't have been as exacting as I would have liked but, let it stand, I've worked out a solution that works well enough for my legacy content.

Please look at:
Archive Path Configuration

You have the ability to custom format the article archive string identically to the way your old system was. It should not require much effort at all.

Using OpenID verification (finally.)

Keep up the great work on your blog. Best wishes WaltDe

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)


October 5, 2005