Yesterday, I upgraded the PHP version on my server from 5.2.4 to 5.2.5. PHP 5.2.5 brings improved "stability of the PHP 5.2.x branch with over 60 bug fixes, several of which are security related". I also reintroduced eAccelerator back onto the server. I stopped using eAccelerator last spring, not so much because I had any real issues with it, but because I spent the summer months hosting my sites on the cheap.
Thanks to a post at OpenSourceCommunity.org, I came across a conversion tool to allow you to import the SMF 1.1 database into a phpBB 3 site. Information about the conversion tool can be found in a forum post at phpbb.com. By the way, the script is still in beta, meaning that it works but you might find some bugs since it is not fully tested.
Last weekend, both Linux Today and Linux.com provided links and excerpts to an article I posted here at CMS Report. You can see some of the stats on my newly quantified site at quantcast.com.
Steven Peck, associated with the Drupal project, wrote about an article he came across regarding a comparison of the vBulletin forum and Drupal's forum. The article is titled, Goodbye vBulletin, Part 1: Reasons to Switch. The author of the article writes:
The aim of this article is not to poke holes, or say ‘vBulletin sucks’, but to provide constructive criticism of a successful product, proving that vBulletin is not always the best choice. In places the article compares vBulletin to Drupal, this is the platform The Webmaster Forums will be switching to and represents many of the things vBulletin should—in our humble opinion—aspire to.
Mr. Peck's reaction to the article (and my emphasis in bold):
Now this was a interesting. A well written article on why one site is switching over to use Drupal's built in forum rather then continue to use vbulletin.
In other words, Peck and many of us that pay attention to how the forum applications stack up against CMS native forums don't see too many articles like this. It is rare to see someone using a standard forum application such as vBulletin, SMF, or phpBB switch over to Drupal primarily for its forum functionality.
If you are reading this post, then congratulations...you are now seeing CMS Report on its new server (a Virtual Private/Dedicated Server). As I tweak the VPS in the following weeks, I may fall back on the old server from time to time but for the most part, I'm home. Today officially ends my grand-experiment of running a moderately busy Drupal site on the cheap.
So, Python isn't really a CMS topic unless you're a Plone user. However, as my world at work slowly moves from Python to Java as the language of choice...I'll promote this underdog open source language anytime. From the IBM developerWorks site:
"It can happen anywhere, at any time. You’re doing your job, minding your own business, and it suddenly dawns on you: you’re the company’s webmaster."
--Shane Schick, "Accidental webmasters rejoice – help is on the way", GlobeandMail.com, September 5, 2007
A few months ago I mentioned that I was hosting my site using a "budget shared hosting plan through my reseller site which is comparable to the hosting plans offered by GoDaddy". In that same article, I also mentioned that although I prefer to run my sites on a Virtual Private/Dedicated Server (VPS/VDS), I wanted to try experimenting with the cheap shared hosting plans despite the plans not offering full MySQL functions such as CREATE TEMPORARY TABLE. For the most part, my sites have been running fine on the shared hosting plans but I wanted better control (oh how I miss Linux command line via secure shell). So, I began searching for a better reseller hosting plan. Unfortunately, my search for the perfect reseller host plan still continues.
I thought my hosting requirements were pretty simple. I wanted a reseller hosting plan that provided CPanel, PHP5, MySQL5, secure shell, and a license to a client billing system such as ClientExec. Oh and I wanted to be sure the hosting plans provided were Drupal friendly. While I host more than just Drupal sites I've found that if the server is configured properly to run Drupal then it can run almost any other PHP-based CMS out there. All in all I wanted a shared hosting plan where I spent less time managing the server, yet had the controls I needed via a Linux shell. Simple enough right? In fact I thought I found a great reseller plan through ResellerZoom (RZ). However, after spending most of my weekend hours trying to work it all out, I've come to the conclusion I'm still looking for something that works better.
If the project leaders and users of your favorite content management system are still debating when they should drop PHP 4 support, it looks like the PHP development team has helped make that decision for them. PHP.net just announced the End of Life for PHP 4. Starting in 2008, only security updates on a case-by-case basis will be provided...and PHP 4 is dead in August 2008.