Tag: import

Moved to WordPress and new domain!

I gave up!

This blog was hacked again and the database taken down. As this is no longer my primary blog (and I post here infrequently now) I decided the best course of action would be to simply take it off my server and give it to WordPress.com to host (the chances of it being hacked there are remote!).

I have wanted to change the domain of the blog for quite some time as well so I decided to combine the two jobs into one.

I already owned TomRaftery.com and it was doing nothing so I decided to use this as it is a more appropriate url for the site.

To upload the site to WordPress.com I first created a blank WordPress.com blog (simply by signing up and verifying email – a 2 second job).

WordPress 15mb Import limit
WordPress 15mb Import limit

Then I went to my old site and created an export file (Tools -> Export) – this downloaded a 24mb xml file to my computer. When I went to the WordPress.com to do the import I spotted that the Import message read “Choose a file from your computer: (Maximum size: 15mb)”. Oops! – this was going to be an issue.

I thought about going into the xml file and manually editing it but when I opened it I saw it was over 400,000 lines long and I really didn’t want to mess it up so I thought again.

I checked the spam list on the site and I saw there were thousands of spam comments in there. What if I deleted them and tried again? I did and sure enough this knocked the xml file size down to 17mb – an improvement but still too large to import. What to do?

WordPress Blog Export options
WordPress Blog Export options

Then I had a brainwave (should have been obvious really) – what if I split the export into two files? So I tried it, I first exported all blog posts up until December 2006 and then I did another export of all the blog posts from January 2007 until the most recent post (November 2010).

This created two files of less than 15mb each which could now be imported. Would WordPress.com allow me to import two files totaling more than 15mb? I didn’t know but figured it couldn’t hurt to try, so try I did and it worked a treat!

Now that all my blog posts (and their associated comments, categories, tags, etc) were imported the next step was to associate it with the TomRaftery.com domain. This required me to update the nameservers for the domain to point to WordPress nameservers (after paying for the domain pointing service from WordPress). Then I had to set it as the primary domain for the site (see below).

WordPress domain management
WordPress domain management

The last step was to go back to the old TomRafteryit.net domain and set a permanent (301) re-direct on it so that people (and search engines) would be re-directed over here to the new TomRaftery.com domain – now safely hosted on WordPress.com servers.

So here we are. If you are reading this – welcome to the old blog on this new site. Thanks for taking the time and hopefully I won’t leave it so long to the next post!

WordPress 2.3 gotchas (or got me's!)

Phew!

Finally done with that install – ouch! I wouldn’t want to go through that again in a hurry.

I hit several speed bumps in my upgrading of this blog from WordPress 2.2 to 2.3 – many of those could have been avoided if I had followed the instructions on the Extended Upgrade page instead of the Upgrade page!

Specifically, if you are upgrading, not only should you also upgrade all plugins before starting the blog update, but you should then disable all plugins before uploading WordPress 2.3.

I use the K2 theme on this site, so I checked it out, and sure enough there is a new version of K2 (K2 RC1) available for WordPress 2.3 as well. If you plan on upgrading to RC1, be aware that Michael Heilemann says in the release notes:

Because so many things have been upgraded since v0.9.6, a lot of the code hasn’t actually seen as much usage as the v0.9.6 code, and thus you should hold off until RC2 with upgrading if you like your stability over your ‘bling’

I decided to try out the widget functionality which comes with K2 RC1 but I came a cropper on a bug in the code and so reverted to using the less functional, but fully operational WordPress Widgets.

One of the biggest advances in WordPress 2.3 is the inclusion of Tags. This is fantastic news for anyone who hasn’t used tags up to now as it provides a simple way for them to begin. However, I was using a plugin (Ultimate Tag Warrior) for my tagging and this no longer works with WordPress 2.3.

WordPress 2.3 has the ability to Import existing Tags though (Manage -> Import -> Ultimate Tag Warrior) meaning all my tagging up to now hasn’t been in vain!

Ultimate Tag Warrior (UTW) had two great features:

  1. UTW presented you with a drop-down of all your previous tags when writing a post so you could easily chose one you had previously. This is missing from 2.3
  2. UTW had a Suggest option whereby it would scan the text of your post and suggest appropriate tags

Christine Davis, the author of UTW has already released plugins to fill in this missing functionality!

Other features added in this release of WordPress are highlighted here.