I began running this website on Drupal 6 shortly after the official release.  Before then, I periodically installed development versions of Drupal 6 on the production server during the weekends so others could judge the progress that was being made.  During this period, I made the claim that I didn't really need any contributed modules to run my site 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.

It could have been a bold statement that I made at the beginning of the year.  Although Drupal 6 interest has finally overtaken Drupal 5, there still are a number of popular modules still under the designation of release candidate, beta, and even alpha.  My site has shown that you don't have to always wait for contributed modules to upgrade a site to the latest version of Drupal.  However, my statement was a lie. By the time Earl Miles released Views 2.0 Beta 1, I found I didn't want to live without my essential modules for very long.

The following are a list of contributed Drupal modules that I wouldn't want to do without here at CMSReport.com.  I am neither the first word nor the last word of which modules you should be running for your Drupal site.  In fact, by coincidence, Kathleen Murtagh has just written a similar list of contributed modules that should be considered.  Some of the modules on my list are still going through their development phase and you'll have to assess the risk of using the modules on your own sites.  Personally, I like to take the risk for my hobby sites such as these, but I am more cautious when using development code for sites managed at my day job.  Whichever modules you choose, be sure to thank the developers that have made your site possible. 

Contributed modules used at CMSReport.com

Sends e-mail to notify both registered and anonymous users about new comments on pages where they have commented. The goal is to drive one-time users that comment back to you site to convert them to real registered users. This conversion step is an essential one in building a blog comment community.

Augustana College, a United States college affiliated with the Evangelical Lutheran Church in America, is using Drupal.  According to Augustana's Web Editor the site was developed by Tim Broeker of Electric Jet (Mnpls) using Drupal 5.  Electric Pulp, a local Sioux Falls company, also contributed to the project by doing the design and CSS work.

I don't think I've ever met Tim Broeker, but what is interesting about this Drupal site developer is that he also has a Joomla! Core Team connection.  Yes indeed, open source does matter.

Packt Publishing announced the five finalists for each category of its 2008 Open Source CMS Award.  Last year, Drupal was the overall winner. Voting for the winners in each of the five categories opens September 1 and ends on October 20, 2008.  This "public vote" will then be combined with votes by a panel of judges for the top three CMS in each category will then be voted for by a panel of judges.

Incidentally, this year I'll be on the panel of judges for the Most Promising Open Source CMS.

Overall Open Source CMS Award

• DotNetNuke
• Drupal
• Joomla!
• Plone
• TYPOlight

Most Promising Open Source CMS

• CMS Made Simple
• ImpressCMS
• MiaCMS
• MemHT
• SilverStripe
  

One of the biggest unknowns for those of us that live in the north central United States...how many Drupal enthusiasts are there in our area?  Not knowing the answer to this question has been bothering me.  I have also been a little disturbed seeing the map so empty of a Drupal user group for my part of the region.  So I'm hoping those of you that are Drupal users from South Dakota and bordering areas will join me and others in the new South Dakota Drupal User Group at groups.drupal.org.

This is a group for those in the state of South Dakota and and the border areas of South Dakota who are interested in Drupal! The number of Drupal users in our area may be small, but our numbers are steadily increasing. Lets get together and chat about all things Drupal whether you are a Drupal user, developer, or Web designer.

Could we have enough people for a Drupal meet-up?  Stay tuned...

Development of the SMFforum Integration module for Drupal is no longer.  Amy Stephen over at OpenSourceCommunity.org pointed out on her blog that the module's project  leader, "vb", pulled the module due to licensing disagreements with SMF LLC.  Amy references vb's original post at the Drupal forum, but she has a lot more to say.  Amy's an active participant in the Joomla! community, a community which had their own issues with a bridge between Joomla! and SMF.

According to vb's post, an email sent by Michael "Oldiesmann" Eshom, Project Manager, Simple Machines LLC stated that:

The problem isn't with the smfforum.module file or the packages distributed on drupal.org. The problem is with the "smf_api_subs.php" file that you're distributing as part of the smf api package - it contains modified versions of several SMF functions, and you did not ask for permission to use this code or distribute it.

It appears that Simple Machines LLC doesn't have so much of a problem with bridging SMF and Drupal as much as they have issues with their own code being used without proper permission.  The Simple Machines License clearly states that "Any Distribution of a Modified Package or derivative requires express written consent from Simple Machines LLC."  No word on whether Simple Machines LLC would endorse the use of their code if permission is asked.

The April issue of Adobe Edge contains the article, Review of open source content management systems. The article provides an overview of what the author describes as "five of the top open source software (OSS) solutions". The five open source CMS included in the author's list are CMS Made Simple, Drupal, Joomla!, WordPress, and XOOPS. After reading the article, I found myself wondering how we "reviewers" can actually improve our reviews of open source CMS. More importantly, I've come to the realization that I can no longer claim to be non-biased in which CMS I believe is the best out there.

The author does a fine job in the article describing the similarities and differences between the CMS being reviewed. However, one of the issues I have in this article and many others I've read that review CMS is the big jumps in the conclusion:

Drupal, Joomla!, and XOOPS are best for building an e-commerce site because all three offer:

• Inventory management
• Support for third-party payment processing mechanisms (such as PayPal)
• Modules for shipping and sales tax calculators
• Shopping cart functionality

While it is true that Drupal, Joomla! and XOOPS can do e-commerce, none of these CMS can do that straight out of the box. I can just imagine a shop owner or design company trying Drupal, Joomla!, or XOOPS for the very first time and wondering, "how the heck do I get a shopping-cart into the CMS?". While the author does hint in the article that third-party modules are needed to make the e-commerce work, I think the author would have been better off better explaining that "some work is required" to get those features into the CMS.

Dries Buytaert, Drupal's project leader, has just unveiled his latest Drupal project...Mollom. Mollom's goal is to be an automated content monitoring system with one of its initial services geared toward providing a spam filter and CAPTCHA server for websites.

Dries Buytaert: Mollom, my content monitoring startup -

After several months of private beta testing, Benjamin Schrauwen and I are happy to unveil Mollom, your partner in automated content monitoring. Mollom's purpose is to dramatically reduce the effort of keeping your websites clean and the quality of their user-generated content high. Currently, Mollom is a spam-killing, one-two punch combination of a state-of-the-art spam filter and CAPTCHA server. We are experimenting with automated content quality assessments, but these are still in an early testing phase.

CMSReport.com is one in a number of Drupal sites that have been "secretly" testing Mollom over the past several months. Since installing Mollom, I've been able to sleep at night knowing that Mollom is watching over my site. The amount of time I spend on moderating anonymous comments for potential spam has been significantly reduced thanks to Mollom. This is good stuff from Dries Buytaert and Benjamin Schrauwen!

Linux.com is featuring a story by Susan Linton titled "Drupal 6 keeps getting better". The author claims she has been using Drupal since version 3.1 and seems to know Drupal well enough to write a decent article. In short, she does a farily nice job of summarizing the features introduced in Drupal 6. However, she ends the article with a rather strange conclusion.

My primary complaint with Drupal is still not addressed in this release. I believe having advertising capabilities is almost a necessity in any content management solution. Instead, Drupal leaves users to their own skills or to use a contributed module. The lack of native advertising support remains a major drawback.

I rarely have seen such request for an "advertisement feature" in the core of any CMS I've reviewed. Yes, some CMS do have an advertisement feature but in most cases the capabilities of such built-in features are usually limited. Either way, I just can't imagine with the latest drive to strip the less needed modules in Drupal 7 and beyond, that the Drupal developers would go for an ad module in the core.