A new home, a new skin, and a new backbone
Best Web Ezy’s New Home
I have just moved this blog into the new hosting environment. As I mentioned before, I am moving this blog to a US based hosting because I figured out that most of the audiences are from the US. And I want to keep my AU based server for the Australasia clients. Therefore recently, I have migrated to Cirtex Hosting.
So far, no complaints. All goes well. Uptime is good, technical support is fast in responding to my emails. If you are looking for a web host, I would suggest you to use Cirtex Hosting.
Best Web Ezy’s New Skin
As you probably have noticed, I have changed the theme of this blog again. This time, it is an SEO friendly theme. I am planning to keep using this theme for a long time. There are a few bits and pieces to be fixed, but generally, I am happy with this.
I chose this skin because it is not the usual John Chow style theme, which you might have noticed a lot of similar themes around. They look like copycats of John Chow. And the color is fresh. It is the 2-column style that I always like to work with. I am still tweaking it a bit as I plan to put a few products of my own here. Talking about that, please look out for my upcoming publication. I am sure (I hope) it would be a good reference for webmasters.
Best Web Ezy’s New Backbone
Last but not least, Wordpress 2.5.1. I was always lazy to upgrade the blog but I thought I should use this chance to upgrade as well. I think this is the best version so far. The admin interface is so different now, but it is so much easier to work with.
I had a bit of problem migrating the database across. There was an encoding problem. Apparently the previous version of Wordpress was using Latin 1 Swedin as encoding method for the MySQL database. When I got it imported into the new version, there are strange words all over the place.
After a bit of search on the internet (well, where else) I have found the solution:
- Export the database into a .sql file
- Change the encoding from Latin1 to utf8
- Import into the new database with utf8 as default encoding
- Edit the wp-config file by commenting out the encoding line
- Upgrade the Wordpress version to 2.5.1
And that’s done. Nice and easy.
