I just finished migrating my blog from blojsom 2.27 to wordpress 2.2. You may be wondering why I would consider this a guilty pleasure. Well, wordpress really is a pleasure to use, but it just happens to be written in PHP. Of course, I really have no desire to start customizing my blog software beyond a few tweaks to the theme, so I really shouldn’t be bothered by this. However, I do see the overabundance of PHP blog/forums/CMS software as a gateway drug to full blown PHP programming. Being a programmer by trade, I realize that I will not always be able to choose the programming language of the projects I work on, and the more PHP developers that exist, the more likely that my job will depend on working with it.
That’s enough negativity, since wordpress is really amazing. I chose wordpress, after reading many reviews of various blog software. Here are the two most significant.
The main deciding factors that caused me to go with self-hosted wordpress versus free blog hosting at blogger or wordpress.com is that I want my own domain name, and I am fascinated with making money from web advertising which blogger & wordpress.com don’t let you do.
When I first installed blojsom, I was interested in getting more experience with java wars (web archives, not Starbucks vs. independent coffee houses), so I am not really disappointed in having to make the switch. I was disappointed with the poor user interface for administering blojsom. To edit a blog post, I would first have to remember or look up the category it belonged to before I would get a drop down list of the posts that I could edit or delete.
The most difficult part about setting up wordpress is creating a mysql database and making sure the file permissions were correct. If you are setting up wordpress for someone else, almost everything can be configured through the admin console except for uploading new themes or plugins. If you upload a new theme, be sure to choose one that is widget-ready.
Here is a short list of cool features in Wordpress:
- While you are writing a post, it is periodically saved so that you don’t lose it if your browser crashes.
- A drag-and-drop interface for adding widgets to your sidebar under Presentation/Widgets in the admin console.
- Gregarious is a very cool social bookmarking plugin.
- You can edit the post in WYSIWYG or HTML mode.
- You easily import your old blog using the Manage/Import page. I used the RSS importer to pull in my blojsom posts. It worked great except for a few line wrapping issues caused by wordpress treating a newline as a <br/>.
Since my old blog was indexed by google, and I didn’t want to break anyone’s bookmarks, I tried to map as many of the old urls to the wordpress blog, using these steps.
- Under Options/Permalinks, I entered this custom permalink structure:
/%postname%.html
Blojsom formats urls as permalinks or as category plus date urls, but both included the title of the article, so I could use mod_rewrite to remove all the extraneous info in the urls. Blojsom also put “.html” at the end of its article urls, which I decided to keep, since I thought a mod_rewrite rule to remove “.html” could affect urls that I never intended to rewrite.
- Here are the rewrite rules that I added to my apache configuration. I did not put these in the .htaccess file, since wordpress wants to put its own rewrite rules in .htaccess, and I wanted my rules to take precedence.
RewriteEngine on # Remove category & date from blojsom style url RewriteRule /[^/]*/200[67]/[0-9]*/[0-9]*/(.*) /$1? [R=permanent] # Convert "/?permalink=foo&extra=bar" to "/foo" RewriteCond %{QUERY_STRING} permalink=([^&]*) RewriteRule /.* /%1? [R=permanent] # Convert "/?flavor=rss2" to "/feed/" for RSS version 2 RewriteCond %{QUERY_STRING} flavor=rss2 RewriteRule /.* /feed/? [R=permanent] # Convert "/?flavor=foo" to "/feed/foo" for RSS version 0.92, ATOM, and RDF. RewriteCond %{QUERY_STRING} flavor=([^&]*) RewriteRule /.* /feed/%1? [R=permanent]

Atom Feed
Thanks for article!
Comment by Agencja Reklamowa PoznaÅ„ — September 10, 2007 @ 5:02 pm
WP comes with some disadvantages too. Compatibility of plugins for instance. If you upgrade your WP, there is no guarantee that your plugins will work. This is not happening too often, but it all depends on updates. For instance, my two plugins (captcha-godfather and cross-linker) were not working on WP 2.5.1 until I fixed them. Also, WP is targeted by spammers too much (just modify the bottom line of your blog saying “powered by WordPress” for example - because spammers find WP blogs this way too).
BTW, if you want to make money (as you’re mentioning within this post) from your blog, you should consider putting ads into the body of your posts. Mark them as sponsored links for instance. Such ads have better CTR, thus they’re better source of income than side-placed ads. And one last thing… I can’t see any sidebar of your blog on my Opera (Opera 9 on Linux Suse). It’s related to invalid XHTML code of this theme for sure. But my FireFox 2 (2.something) shows your blog fine. Don’t take this badly, I just wanted to tell you about something what’s not working properly for everyone.
Comment by Jan the aquarium guy — June 23, 2008 @ 4:50 pm