Switching from Community Server to WordPress

The last time I started blogging, I chose Telligent’s .TEXT (later renamed to Community Server) after some research on the options available. It was the sensible choice at that time because

1- It used the (then hot) .NET with SQL Server, which I was playing with.
2- It was Open Source.
3- I had a feeling the community will contribute and extend the functionality through its (pretty good) plugin-based architecture.
4- Though I did not need its forums, the photogallery was really powerful.

The post (one of the few I managed to post) about my installation experience, and enabling anonymous comments did help out a couple of people so I feel less guilty about not continuing to blog.

Fast forward a couple of years… I am restarting blogging and searching for the latest version of community server and it turns out they are not “serving the community” anymore and have gone commercial. Yes they do still have a “free” license, but no its restricted features no longer suit or attract me. So I have to either stick to the older version, install the new version with all the restrictions, or switch to another blogging system.

As you can see, I chose the last option and switched to WordPress, after another two hours of research to see what has been happening in the blogosphere while I was away. I feel sorry for the people who can’t switch due to lack of web applications deployment knowledge (drop me a message if you need help), and I am glad to see about 2 million results in Google for “community server” vs. 12 millionish for WordPress. One more win for the REAL opensource!

I use a free redirection service from www.mydomain.com which points www.reallyvirtual.com domain to the rv.cypherone.com subdomain, this way I can use my existing hosting for the blog, until I find a reason to get a dedicated hosting space (1000+ readers ought to be a good reason 🙂 ). My hosting provider is webhost4life.com, which has real human (and fast) support and had the best value for money that I could find at that time.
Now webhost4life has a decent set of ready-to-install plugins (WordPress included), which I immediately set up using their single click install, only to find out it was an older version (2.0).
The WordPress upgrade documentation page made upgrade sound like a painless process, but after upgrading, I somehow ended up with only my homepage displaying, with all other links giving a 404. Back to Google I went… at first I thought that WordPress in getting confused by the base URI (www.reallyvirtual.com) and the redirection, but found out later that since the server is windows based, so a combination of mod_rewrite and .htaccess unavailability, if you try to use custom (pretty) permalinks, could do this. *SIGH*

I decided to start with a clean slate, and after a few minutes of tinkering around, finally found the php.ini solution to WordPress permalinks error that works for me. Thanks Taragana 🙂

After installation from scratch, tweaking the basic settings, creating categories for topics that I plan to write about, and being impressed with the range of plugins available (Community Server doesn’t even come close here), I can now safely say WordPress is the best choice at this point in time. The only thing I still need is a photogallery to go with it. If you have any recommendations, do let me know.

2 thoughts on “Switching from Community Server to WordPress”

  1. WordPress does rock, but you’ll want to set up Akismet, or your bot will be overrun by spams like the above.

Comments are closed.