Drupal

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.

Jeff WhatCott, Acquia, asked some important and thought provoking questions on his blog, "A Dormant Drupal Opportunity". While the post focuses on Drupal, I think the contents of his post can apply to almost any content management system (CMS) out there.

In the article, Jeff asks whether defining Drupal as a CMS does more harm than good in describing the scope of features Drupal has to offer. In his words, the term CMS is a "20th century term that completely undersells what Drupal is capable of" as social software and a means for collaboration. Considering I really didn't understand what a CMS was until the 21st century, I beg to differ that the term CMS is as ancient as he makes it sound. However, he is entirely correct...many of today's Web applications that we call a CMS, really are not just a CMS.

Jeff asks three questions in his post:

1. Do you think we should put the CMS term to bed?
2. Would it be possible to grab some of that team collaboration social software market opportunity for the Drupal community?
3. Why isn’t there already a billion dollar Drupal services ecosystem for team collaboration? What’s missing?

While I appreciate comments here, please be sure to go over to Jeff's post and respond there too. In fact, if you only want to comment at one site...go there so we don't steal any of Jeff's "thunder". I've already made my comments at his site and I've attached my response to the above questions below.

I'm looking forward to evaluating the new FeedAPI module for Drupal. Though one feature I haven't seen in any of the aggregators I've seen so far for Drupal...a way to snip the original RSS feed. Some sites provide you the entire post in the RSS feed with no teaser. This may be great for the reader, but I'm not sure everyone is happy to see their entire post on someone else's site.

From time to time, I've hacked the core to get me closer to how I would like the content from an RSS feed to display at my site. There has to be another way and perhaps FeedAPI could by my solution...

Development Seed: FeedAPI 1.0 Released -

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.

In 2006, I helped bring a friend's Fish and Tackle store online using open source osCommerce. The project was ugly in both appearance and code as I was merging a legacy site with an SMF forum together with the osCommerce software. As I indicated back then, while osCommerce was functional I was not pleased with the software. I kept on thinking how much easier this project would have been if I had used what I consider as modern CMS's. Specifically, I was thinking Drupal and perhaps even Joomla!.

Except for some Python programming, I've done very little software development this decade with most of my efforts in the 80's and 90's (BASIC, Pascal, Perl, Tcl, etc). Those that know me know I've wanted to dig more into PHP and Ruby, but I have been distracted by one sorry excuse after another.

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.

"While Drupal's growth is impressive, it won't be reaching its potential if it resists incorporating learnings from other systems (e.g. 'this is Drupal, not Wordpress')."

- theneemies, "Chris Messina's Drupal 6 review", Open Source Community, November 14, 2007

A couple months ago, I experienced a number of errors at my Drupal site that all pointed to a corrupted database. I believe the problem likely was the caused by a sloppy export/import I performed with the MySQL database while moving the site to a new server.

While my particular database problem was an easy fix, if you really don't know much about databases you may find that you really need some guidance on how to solve problems like these. This article is the process I went through to correct this particular MySQL database problem in Drupal 5 and some general database rules that show why this problem occurred in the first place.