The second time I tried to import the old blog, everything went as planned, although all the embedded YouTube links have broken. Some image placements are slightly wonky due to a kludge I used at Blogger to get the vertical spacing the way I liked it.
My feed should be working now; let’s see if this shows up at Facebook.
All I have left to do is add my links, categorize my 740 posts (because I like making work for myself, apparently), and create a .htaccess file to 301-redirect the URLs of my old blog to here. That’s important because it tells the search engines that this new blog is the same as the old one only in a different place. I don’t want to lose my inexplicable Google rank for “early senility”, after all.
Anyone who links to the old blog can change the URL – or not. The redirection takes care of that, of course.
This WordPress blog seems to load a bit more slowly than the Blogger version but considering how bloated it is (beauty has its price), that’s not surprising.
I think I can live with the vertically offset legacy images.
101 is open for business!
Update: I finally got the .htaccess file working after 90 minutes of excruciating frustration. My problem? The file in plain text on Mac OS X uses carriage returns. Linux requires linefeeds. Once again, Tex-Edit Plus comes in handy. I’ve been using it since 1994 and I paid many times the recommended software price when I bought it back then. Thanks, Tom Bender.
With layout in place, I decided to move my blog from Blogger to this WordPress thing the kids are crazy about. That sounds hard, but it’s not difficult in theory. WordPress offers all kinds of import tools. The one that interfaces with Blogger, though, requires the blog to be in the new Blogger format, a change I resisted and continue to resist with all my Luddite mightiness.
That’s not the end of the world, since Blogger lets you export the content all your blog posts as one XML file, which you can then upload with WordPress. WordPress reads the code and reassembles the posts. Unfortunately, WordPress will only do that for the new-style Blogger blogs.
Not all is lost. Google provides a little Web-based engine that will convert the old-style Blogger XML file to WordPress format. WordPress should import its own format.
But that has issues, too.
Still, with some perseverance, I got the thing to work. I watched my Blogger posts get imported, but some of those posts weren’t mine. Somehow, my XML file was infected with blog posts from Jennifer’s Just a Stray Junior Mint. I don’t understand how or why either, but it happened in the conversion process.
I had to manually delete Jennifer’s posts from my archive and in the process I discovered that the import process only snagged my posts up to the end of 2008. WordPress documentation tells me that I can rerun the process without duplicating those posts that were successfully imported.
I actually have a lot to blog about: hockey, new pets, “Avatar”, “The Pacific”, “Glee”, and a figurative kick in the nuts.
So much for the rule of three, eh?
With Blogger abandoning FTP publishing in a month and a half, I’m at a crossroads. Do I create a subdomain at 101squadron.com (hosted at Blogger’s Blogspot) for the blog or do I move to WordPress? I’m trying to limit my posting until I make that decision. Advice?