[UPDATE: Please see response from Trevor Johns in comments]

I decided that seeing as we were shutting down one of our older servers, one that has housed my blog for a few years… I would spend a bit of time upgrading it. Hopefully give my self more motivation to post again.

In that process, I decided to go with blogger.com – initially I thought this was a good idea! Easy to use interface, uses my google account to log in, less server load as it’s all HTML on our server.

The problem that I have though – is I have an existing blog. Not a super prolific one, but I get a couple of hundred uniques a day. I would like to keep my content that, for whatever reason, seems of interested to some people.

Blogger.com currently has no way of importing data. Of course, there is an import in the Draft version of blogger, but that is useless – as it is only intended to import other blogger blogs XML backups.

There are a heap of scripts out there that can help push your posts back in to your blog via the blogger api – again, whilst the work that the coders have done on them is fantastic – bloggers api is… crap.

As part of their measures to fight spam, or whatever… The api allows your code to post about 22 blog entries in any given 24 hour period. It then silently drops the other posts. It responds with an affirmative response code for each call to the api – giving your application the impression that it has posted. The reality however is that the words that you have poured out of your heart and into the keyboard have simply been forwarded to /dev/null.

All of this has essentially prompted me to upgrade properly and move across to the new server. So, here my new blog sits… using a generic template until I have time. On a shiny new hosting slot on our server. And there blogger sits – listed on WhatShitsMe.com.

Agree, disagree? Tell somebody!

• 

The WordPress to Blogger.com… mistake! by Troy Kelly, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.