Life of a Startup Founder - Silicon Valley Blog

Moving from Typepad to Wordpress - How To ( Part 1 )

by Vic

In the last post on Moving from Typepad to Wordpress, I gave the outline of pains of migrating from Typepad to Wordpress. Lets continue where I left in the last post.

Lets talk about the following 5 issues and how I solved them here.

Typepad uses short weired urls’s for each post while Wordpress uses SEO friendly URL’s
Typepad adds .html at the end of each URL while Wordpress doesn’t
Typepad blog name is problematic ‘myblogingsite.typepad.com/blog1’ - the second part ‘hotfromsiliconvalley’ after the slash in the URL host name is the name you choose when you were setting up your blog on Typepad.
All the links in blog posts before I mapped my Typepad blog to my own custom domain name, still point to Typepad.com
All the file links and logo links are still pointing to typepad.com

1. Typepad uses short wiered urls’s for each post while Wordpress uses SEO friendly URL’s

Lets take an example for a post, url generated by Typepad is ‘http://hotfromsiliconvalley.com/hotfromsiliconvalley/2007/06/gps_that_never_.html’ while this post is imported in Wordpress, the URL generated by Wordpress would be ‘http:// hotfromsiliconvalley.com/hotfromsiliconvalley/2007/06/18/gps-that-never-fails/’ provided that permalinks are enabled in Wordpress. That is where wordpress slug feature comes to the rescue. Wordpress lets you manually assign a post slug to any post, which overrides automatically Wordpress generated SEO friendly post slug.

However, you have to manually open each post in wordpress and assign it a post slug manually. I copied the old Typepad post slug ‘gps_that_never_’ in the Post slug box on the post management page. Now the URL generated by Wordpress was ‘http:// hotfromsiliconvalley.com/hotfromsiliconvalley/2007/06/18/gps_that_never_/’. Looks like that we are getting closer.

2. Typepad adds .html at the end of each URL while Wordpress doesn’t

Next step is adding .html at the end of all URL’s automatically and getting rid of that last ‘/’. Also in the posts URL structure Typepad is using /Year/Month/ while the default for Wordpress is /Year/Month/Day/, so will be dropping this /Day part from the URL generation as well.

We can achieve this simply by configuring the Wordpress’s permalink generating structure and customizing it. Tell Wordpress to generate custom structure using the following string ‘/%year%/%monthnum%/%postname%.html’. We have done 3 things here. We have removed the /%day% , added the .html to the end of each URL and removed the postfix ‘/’ from each URL.

After updating the Permalink structure, now the finished URL is ‘http://hotfromsiliconvalley.com/hotfromsiliconvalley/2007/06/gps_that_never_.html’ - Hurray, this is what we wanted.

3. Typepad blog name is problematic ‘http://hotfromsiliconvalley.com/hotfromsiliconvalley’ - the second part ‘hotfromsiliconvalley’ after the ‘/’ in the URL host name is the name you choose when you were setting up your blog on Typepad.

Solution for this is very simple. I simple choose to install the Typepad software in a subdirectory named ‘hotfromsiliconvalley’ instead of installing in the root web directory and that did the trick because automatically ads the subdirectory name as part of the URL.

Another way this problem could have been solved would be by modifying the permalink custom structure in Wordpress, if you had installed the wordpress in the web root directory of the server. The Custom Structure for permalinks would be ‘/hotfromsiliconvalley/%year%/%monthnum%/%postname%.html’, and that will inject ‘hotfromsiliconvalley’ after hostname in the URL.

4. All the links in blog posts before I mapped my Typepad blog to my own custom domain name, still point to Typepad.com

For this the solution is a search and replace operation on the text file which was exported by Typepad. You have to this before you import this file in Wordpress. In your favorite text editor search for ‘http://hotfromsiliconvalley.typepad.com/hotfromsiliconvalley/2007’ and replace it with ‘http://hotfromsiliconvalley.com/hotfromsiliconvalley/2007’ throughout the document and that should do the trick. Repeat the same for all with the other years 2006, 2005 and so on. This ensures the image URL’s are not automatically replaced in this operation and they will continue to point to Typepad, which we can replace next.

5. All the file links and logo links are still pointing to typepad.com

This one is going to be a semi-automatic operation. In the same file you exported from Typepad, search for the following URL, and repeat the search with other years like 2006, 2005 etc. Search for ‘http://hotfromsiliconvalley.typepad.com/hotfromsiliconvalley/images/2007’ and manually replace this line with the new location for the image. You have to be careful with this manual search and replace operation as the chances of making the mistake is very high. You have to also trim /month/day which is after the /2007/ year part. In Wordpress the default location for images is wp-content/uploads/ directory. So the URL for the images would be ‘http://hotfromsiliconvalley.com/hotfromsiliconvalley/wp-content/uploads/’.

But there is another problem - How will you move all your pictures from Typepad to Wodpress. Typepad does not allow you to export the pictures (at least I couldn’t find that option). So how to get or export your images out of Typepad pad so that you can now user them with your Wordpress blog? There is a little trick we can play with Firefox to unlock all your files… that will be for the next post tomorrow.

Moving from Typepad to Wordpress - pains and problems

by Vic Podcaster

2 Comments

After starting out with ‘hotfromsiliconvalley.typepad.com’, for quite a while I’ve been using my own domain name ‘www.hotfromsiliconvalley.com’ for my Typepad blog. When I decided to move from Typepad to Wordpress, I had thought that moving from the Typepad to Wordpress would be simple, easy and straight forward. Why - because Typepad allows you to export your whole blog to a text while, and Wordpress supports importing your Typepad blog. Since I owned my own domain name, I would retain my Google page-rank and all the inbound links will remain intact. Oh! I was so very wrong.

If you are the text only blogger than nothing to worry about, provided you have your own custom domain name. Not me, well I use lot of audio (podcasts), photos and logos. I had approximately 300 media rich posts on my Typepad blog. Exporting the content of the blog from the Typepad in a human readable text file was the only easy part and takes less than a minute. Now I imported this text file in Wordpress by going to Manage - Import - Movable Type and TypePad, and volla, in less than 5 minutes, I had all my posts including comments and trackbacks show up in Wordpress. And that is where the easy part ends and my jaw drops. Why?

Typepad uses short weired urls’s for each post while Wordpress uses SEO friendly URL’s
Typepad adds .html at the end of each URL while Wordpress doesn’t
Typepad blog name is problametic ‘myblogingsite.typepad.com/blog1’ - the second part ‘blog1’ after the slash is the name you choose when setting up your blog, and it is required that you have something here
All the links in blog posts before I mapped my Typepad blog to my own custom domain name, still point to Typepad.com
All the file links and logo links are still pointing to typepad.com
Typepad uses /year/month/my_post_url.html format for generating URL’s while the wordpress permalink uses /year/month/day/my-post-url-that-is-seo-friendly
Typepad does not give me an option to export my media files
Typepad does not let me export my pictures (or I couldn’t find it at least)
Even though, I am using my custom domain name, all posts are still accessible using ‘myblogingsite.typepad.com/blog1′ url and there is no way to switch it off
Typepad does not allow me set up a permanent 301 redirect from old Typepad.com address to my mydomain.com

Basically Typepad is telling me not to leave and stay on Typepad.com for ever. If you do not have your own custom domain name like ‘yourdomain.com’, your blog link life will end here if you decide to migrate as all the links will become orphan, and you have to start all over again.

Well Wordpress came to the rescue. Many many thanks to Matt of Wordpress and the Wordpress community for making Wordpress so flexible. A few surgical tweaks in Wordpress, a few plugins for firefox, a few plugins for Wordpress and I was in business.

OpenSource rocks and I love it more that ever before. Geeks rock.

How I handled these pains, problems and issues? continued in the next post…

Good Morning Silicon Valley

by Vic Podcaster

0 Comments

Good Morning Silicon Valley. Today is the day I had promised that I will start blogging about the adventures and challenges of my startup life, so here is the first post.Welcome to you all to my startup life blog. This blog will give you a peek in the life of a startup founder, and that is me.

Why such a late good morning? Well I crashed this morning around 7 to take a nap after working almost non-stop on migrating my blog and media from Typepad to Wordpress. I have been working on it for quite a while and looks like I am only ~~20%~~ 4o% done. Not good.

It was quite late in the day when I got up, a quick shower and I am back at the keyboard. Looking at the task list it looks like that the migration from Typepad to Wordpress is becoming a mini-project in it-self. Well, I love challenges and surprises, so I guess it is all fair game.

I am done reading my RSS feeds and have a sort of plan for the day. Let me take a short break, and I will write about the challenges, issues, and the things to watch out for when migrating your blog from Typepad to Wordpress.

Moving from Typepad to Wordpress - How To ( Part 1 )

Moving from Typepad to Wordpress - pains and problems

Good Morning Silicon Valley

Subscribe

Translate