Attackr.com

Recently I convinced my brother to move from a hosted WordPress.com blog that was doing rather well, to a self-hosted WordPress blog.

After all, I had the hosting in place, web hosts offer so much nowadays that you can’t use more than a small percent of it. Not to mention he had a chance to make some real money off his own hard work.

It sounded rather simple in my mind:

1. Buy domain
2. Setup said domain on my web host
3. Install WordPress on the new site
4. Configure settings
5. Themes, plug ins, etc
6. Export WordPress XML from WordPress.com blog
7. Import into the new setup

Looking back, that was a rather nice fantasy. If only it was that easy, I’d not be posting this right now.

What happened in summary was this:

1. Bought domain
2. Setup said domain on my web host
3. Installed WordPress on the new site
4. Configured settings
5. Themes, plug ins, etc
6. Exported WordPress XML from WordPress.com blog

And then the fun nightmare started.

Let’s see what all issues cropped up as I intended to simply Import the XML file into the fresh install of WordPress on my host, keeping in mind, this is an XML generated by WordPress.com in their own special layout and destined for import into their own WordPress product, the only difference being its not hosted by them.

• Opened Import page within new WordPress Dashboard, Manage–>Import–>WordPress (there are a nice selection of Import choices)
• My host seems to have configured the php.ini file on their end to max the upload file size to 2MB, whereas WordPress had generated a 4.7MB file for me to upload. Normally this file wouldn’t be so big, but the blog had many, many images that were uploaded to WordPress.com
• That started my search on how to change the limit in PHP. I ended up contacting my host and starting a thread on WordPress.org’s support forum. After much back and forth and a lot of reading on my own, I had worked out I needed a script to fetch the web hosts php.ini file, make changes to it via that script and write it to my /home/ directory. In my case I’d need to only do this once as all I wanted was a temporary increase in the upload limit, whereas those wanting that limit to remain would need to create a cron job running the script daily, so as to keep abreast of any changes made to the web hosts php.ini file pre-adding their own changes.
• With that done, I was finally able to upload the XML file into the new WordPress installation…yay! NOT.
• This is where it got really bad, because the file was so large, after uploading the file it would import all the posts, comments, pages, etc into the new setup, and this was done in real time displaying the details on the web page, coincidentally if a php process takes more than 30seconds, my web hosts php.ini file says that it should kill the process, ding…Houtson we have a problem!
• So I go back, remake my new php.ini file to make sure the time limit is raised to a decent 300seconds and re-do the upload/import process. By now I have 5% of the posts and pages in the blog and it’s looking a right mess. That’s ok really, because after about half a dozen tries, and the import process not stopping half-way it finally reached the end. Breathe.
• What WordPress decides to do is tag every image that was ever uploaded into the WordPress.com blog (Note: The images would have to be moved over manually…more work, eh) was tagged with an ID and placed in the Manage–>Upload section (pic). It also decides to link to the now non-existent image files all on its own (pic).
• Not content having to re-upload every image from the WordPress.com blog over to the new host, editing every page and post for image links, we now had a huge amount of ‘dead’ files under the Upload section, which as I said, didn’t exist. I also think this is why the exported XML file was so big to begin with.

After much debate, we’ve decided to either ask the kind people at WordPress.com to delete all the images off the original blog and thus save us the hassle of exporting it incorrectly.

Either that or follow a very good idea by muhtar on WordPress.org’s support forum, where his suggestion is simple, yet ingenious.
Run a php/db server on your home machine, easy and free.

1. Import the XML file into a fresh WordPress install (again on the home machine acting like a server, running Windows XP if you like), this is way better than to a hosted server, because at home its all instant and no lag to a far off server.
2. Export it to a common format, i.e. SQL and import it into your self-hosted WordPress install (the new domain).

OK, so it’s not easy…but way less error-prone and hair-pulling this way. I guess many have had no issues, the moral here is, don’t assume it’s gonna be so easy to move over.

Better yet, make a good choice to begin with

Originally posted at techzonline.net

Related Posts:

• WordPress 2.5 Shortcodes
• WordPress Tip-Disable Visual Editor
• Simple Guide to Monetizing your Blog
• WordPress 2.5: First Impressions
• Fine-Tune Your Flash Drive