1. File extensions: You can change them from html to php, and many people do. This is wonderful, except where the html page sticks around. Often, the default page is index.html. This is especially problematic when you're updating templates and wondering why nothing seems to work.

Try manually typing in yoururl/index.htm and yoururl/index.php to check this. Remove the html file if this is indeed causing you problems.

2. No way to leave comments (Archive mapping problem): This may not happen for all installations. Under Settings/Publishing/Archive mapping, it will show you what arhcive files will be generated.

In this case, under individual entry, Category Archive and Individual entry archive are being generated in the same place with the same name. Not so good. Individual Entry is selected as preferred, so you might imagine it's the active one of the two. Unfortunately, this isn't the case and it means that it is generated first, and subsequently clobbered by the Category Archive.

There were fairly minimal visual differences between the two templates in this case - with the exception that Category Archives don't allow you to leave a comment. Clicking on the "Comments" link was meant to take you to the Individual Entry where you could post a comment, but as that had been overwritten with the Category archive... Like a circle in a spiral, like a wheel within a wheel. It was impossible to leave comments.

Solution: Delete the Category archive entry from under "Archive Type: Individual" and rebuild.

3. MT3.2b & Typekey Version 1.1: If, after logging in on the Typekey server and returning to the comments page, you are greeted with "Comment Submission Error Your comment submission failed for the following reasons: The sign-in validation failed.", you are experienceing this problem.

If 3.2b is configured with TypeKey V1.1, it needs to get a v1.1 response from the typekey servers to work. But (in some installations) it doesn't actually tell the TypeKey server that it needs that version. TypeKey merrily sends back the standard v1.0 response. Which doesn't work.

Soulution: Edit your Individual Archive Entry template and demand a version 1.1 response, by changing this:

<a href="<$MTRemoteSignInLink static="1"$>"> Sign in</a>

into this

<a href="<$MTRemoteSignInLink static="1"$>&v=1.1"> Sign in</a>


4. TypeKey #2 - Configuration: If you're getting a "TypeKey not configured" error when trying to log in to comment, login to www.typkey.com and check your TypeKey account. Under "YOUR WEBLOG PREFERENCES", the urls you enter should be the server, not your weblog. In my case, it is "http://www.moreblogsofroleplay.com/" rather than "http://www.moreblogsofroleplay.com/Meathe".