I found there's something odd when I comment on the blog I've created. After commenting, I clicked "Sign Out", and the browser redirected me to the url "www.typekey.com" and some strange characters, and then the encoded version of the post link. You know, that %2f things. I thought movable type force me to use typekey service, because to return to the post after signing out, you must visit typekey.com to be redirected back to your post.
I don't like it. I actually expecting comments from registered-user on my system. Although I also like to install another plugins to enable authentications like OpenID, Google, Wordpress OpenID, and two built-ins like livejournal and vox, I think this is annoying. Redirections make people (in this case, my friends registered in the system) who have a slow connection spend time longer, waiting for the browser to open typekey.com, then typekey redirected back to the blog post. I want no redirection, so people who sign out after commenting can return back to the post easily.
Using the findstr in windows (why, no one told me that the command line have so many powers, unlike GUI.) I searched for "typekey" and found it at core.pm. then, I searched "SignOffURL", after I found the line, I deleted the links. [that means, the variable SignOffURL, the global variable for movable type, is empty by now] After conducting this act, I checked mt-comment.cgi that lead me to MT/App/Comments.pm and in that file I searched again "SignOffURL" and in the line that says: SignOffURL . "&return=, " . MT::Util::encodeurl($target), and changed it into SignOffURL . "" . $target, closed all files. Then I tried to comment again, log in using a registered account, give comment, then clicked sign out.
Voila, I've got no redirection. (actually, the browser redirect me directly to the post, instead of redirecting me to typekey, and waiting typekey to redirect me again to the post.)
It succeeded. But I wonder, am I making a mistake by removing this annoying typekey redirection? Is there any error produced by doing this modification? I have no knowledge about this.
In Movable Type 3 we used TypeKey exclusively for comment authentication. This was handled within the templates themselves.
When you upgrade your version of MT to MT4, we do not (as a rule) touch your templates. This may account for the fact that your users are still being forced through TypeKey even though you may have set your blog preferences to turn on user registration and OpenID support.
To take advantage of Movable Type 4's new authentication options you will need to update your templates to use MT4's new comment form.
Instructions on how to do this can be found here.
.