Now, WordPress installation in this domain (
orangescale.com) powers my other blog — in Bahasa Indonesia, using WordPress 3.0 Multi-Site feature. I decided to use this method so that I don’t have to manage two separated WordPress installation. In short: orangescale.com and thomas.or.id are now using a single WordPress installation, using
orangescale.com as the primary blog.
This method works on my blog, but I don’t guarantee that you will have the exact process depending your own installation:
- First, enable WordPress 3.0 Multi-Site feature
- You should have access to modify domain DNS record. If your webhosting provider provide “Add-on domain” feature, it should work.
- Create a new site under First Blog, you can use any address first.
- Export contents from blog you want to move using WordPress export feature.
- Import the export file you have to Second Blog.
- Copy all media files from Second Blog to
firstblog.com/wp-content/blogs.dir/files/X/(Note: “X” is the Site ID).
- Check all settings, escpecially the image locations in your posts. Later, the uploaded media files will use this path:
seconddomain.com/files/path/to/image.jpg(the path might be different). If you have broken image path, check the settings and paths again.
- Install WordPress MU Domain Mapping plugin. Follow the instruction. It’s easy.
- Modify Second Blog DNS settings. Basically, you need to create an A record. Point your Second Blog domain to an IP address used by First Blog.
- Check all plugins, blog settings, and permalink.
I don’t know whether it’s an easy process or not, but here I want to show you that WordPress 3.0 Multi-Site feature can be useful. If you’re still comfortable to manage multiple blog installations, you don’t need to use this method.
It’s not a problem-free solution, of course. And it might be tricky sometimes. For example, about the plugin activation. Which plugins should be installed ‘globally’ or ‘locally’. Some plugins might work without any modifications. Here, I still have a plugin that does not work on my Second Blog. It works well on my primary blog, but not on the secondary. So far, I’m happy with the result.