Content Management

Open Source Community was the first place I saw mentioning an error in a post at Mashable.com regarding Drupal 6. OSC's article is Mashable Blunders, Cleans it up, and Moves on!

A few days ago, I mentioned that "Drupal 6 feels ready to me" for public release. Evidently, that was more than feeling as Drupal 6 was released early Wednesday morning.

Yesterday evening, I spent about two hours updating my site from Drupal 5 to Drupal 6 RC 4 for another weekend test at my site. About 30 minutes was spent backing up the site and installing Drupal 6. The rest of my time was spent with tweaking things via Drupal's admin menus as well as looking at the contributed modules and themes available for D6. I'm currently using the Salamander theme and only two contributed modules, Image and CAPTCHA. I also spent some time placing snippets of PHP code in my blocks to replace many of the functions I was doing with Views. The end result is that with only two hours of work, I am just fine running CMSReport.com on Drupal 6

As I said last week, it's amazing how many people overlook the power of Drupal...even without its contributed modules. Yes, I'll be glad when the Views, Panels, and even the TinyMCE contributed modules are ready to use with Drupal 6. But I've always looked at contributed modules as modules of convenience and not necessity. I'm convinced that most people do not have to wait for Views to move onto Drupal 6. Views only automated a number of SQL tasks that can easily be done with PHP. Some Drupal users are going to object when I say it is "easy" because they are not PHP developers, but you know what, I'm not a PHP developer either. In fact, I'm kind of slow, but I seem to manage along just fine with D6.

As usual during this period of the development process, people are wondering if the new version of Drupal is ready to be released or if there will be another release candidate. Whether this is the last release candidate or not for Drupal 6 I'm not sure anyone can really say. All I will say is Drupal 6 feels ready to me.

As most Drupal users already know by now, Drupal 6 is currently at a Release Candidate 3 stage of development. For the Drupal community, this is a time when the developers are wanting people to test, report, and help fix any bugs found in these development version of the Drupal software. At this stage of development, Drupal.org still does not recommend Drupal 6 to be ran on the production server.

As with everything still in development, we do not recommend running release candidates on a live site. Also, always be sure to make a backup of your data before performing any upgrade or starting testing.

I briefly wanted to mention that the stable release of Joomla! 1.5 has finally arrived! Needless to say, there are some very happy people in the open source community to see this version of the content management system go gold.

I haven't taken a serious look at Joomla! 1.5 since Beta 1 and Beta 2 were out the door. Needless to say, I'm looking forward to taking a look at the finished product over the course of the next few weeks. Until then, below is a brief glimpse from the announcement at Joomla.org of what you can expect from version 1.5.

Matt Mullenweg announced this morning that WordPress.com users will now have 3 GB of free drive space for their blogs. Previously, WordPress.com only offered 50 MB of free space to those that signed up for the free service. Why are they doing this? Looks like Wordpress.com has no longer decided to play nice guy against their biggest competitors, TypePad and Blogger.

The following is an excerpt from Mullenweg's announcement at WordPress.com:

Yes, WordPress and XOOPS are two completely separate projects, but they do have at least one thing in common. Both Web applications were updated this past week to address known security vulnerabilities.

WordPress 2.3.2 was released to fix some very significant security bugs. The release addresses an exploit that can be used to expose your draft posts. WordPress 2.3.2 also "suppresses some error messages that can give away information about your database table structure and limits and stops some information leaks in the XML-RPC and APP implementations".

Drupal 6.0 Beta 3 was released just before the Thanksgiving holiday. As in the past, I wanted to use CMSReport.com as a "live" test site for the beta/release candidates of Drupal as I did with Drupal 4.7 and Drupal 5. However, as this site has matured, so has my reliance on too many contributed modules currently not supporting Drupal 6. So for now, I've decided to place Drupal 6 in a subdomain, drupal6.cmsreport.com.

I am excited with what I have already seen in Drupal 6. I consider version 6 to be Drupal on steroids. Drupal 6 has a lot of performance and power improvements that are already apparent even in the Beta. Put it this way, the day the Views module is ready for Drupal 6, is the day I go live with running CMS Report on Drupal 6.

Packt Publishing announced that Drupal has won their Overall 2007 Open Source Content Management System Award.

After three intense months of voting, Packt Publishing can today announce that Drupal has won the Overall 2007 Open Source CMS Award. With 18,000 votes on Packt’s website, coupled with the expert opinions from a panel of judges, Drupal succeeds Joomla! as the overall winner and receives a cheque for $5,000.

By golly, Joomla has been awarded as the Best PHP Open Soure CMS in Packt Publishing's 2007 awards.

Joomla! is today revealed as the Award's third category winner, claiming Best Open Source PHP Content Management System. Last year's overall winner came out on top ahead of Drupal in second and e107 in third place and receives $2,000.

Joomla! was selected as the winner in the Best PHP category due to "its good front-end for administrators and end-users, which gives users a simple and traditional company website straight out of the box".