I’ve now done another install of WordPress using my WordPress install instructions, and I found a couple places where I could simplify the instructions.
But, the real reason I am responding to my own post is in hope of saving you from the couple of hours I spent yelling at my monitor when WordPress sent me into an endless loop of not being able to log in. The first login would work, but disaster struck as soon as I logged out. I had to wipe out the database and rerun the install script in order to log in again. Of course, as soon as I logged out, I was stuck again.
Finally, I found this post in the WordPress Beta Discussion forum. Due to a bug/limitation in WordPress 1.2 RC1, you can’t have your blog directory and your WordPress install directory be sibling directories. For example, example.com/blog/ and example.com/wordpress/ spells disaster. Or at least, it spells login nightmare.
The problem comes from how the WordPress developers are using cookies. Although someone posted a partial workaround in that thread, I saw a response in another thread from a WordPress implying that this might be a security risk. Hopefully they will fix this problem before the official 1.2 release.
In my first install, I published the blog content directly into my root directory and put WordPress into a sub-directory of the root directory. That configuration works fine. For my second install, I ended up putting the WordPress install directory inside of a blog directory, i.e., example.com/blog/wordpress/. That config also works.
I have updated my install notes to include this new information.
And to address Caveat 2 from my previous post, I did migrate my old MT posts. The export/import went without a hitch. I even took the opportunity to clean up some absolutely horrid HTML generated by Radio Userland, which was the blogging tool I started out using.
I also set up some .htaccess files (using tips from the WordPress masters) to redirect my old MT pages to the equivalent WordPress pages. Details are, of course, on my blog.