Planet Drupal

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 fairly 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.

You and I have a dirty little secret. Many of the Web applications that we call content management systems (Web CMS) are not really content management systems. Huh? A lot of this confusion stems from the difficulty most of us have in answering what should be a simple question, what is a content management system? Scott Abel, The Content Wranger, has noted in previous comments that one of the problems in discussions about content management is that we really lack a common definition of CMS.

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.

During the past couple years I have recommended to people that they host their Drupal sites on a virtual private server (VPS) instead of a shared hosting plan.   While a large number of people do not have problems running Drupal under shared hosting plans, I have always felt that there are less headaches with using a VPS to host your sites.  For example, with a VPS I don't have to worry whether the shared hosting plan gives me the necessary MySQL privileges needed by Drupal (especially CREATE TEMPORARY TABLES and LOCK TABLES).  From time to time, you also hear from people with "Drupal friendly" shared hosting plans eventually find that their hosting company isn't so friendly toward their Drupal site.  Planet Drupal contributor, Clancy Ratliff, is one of the most recent  examples for having a host provider not really happy she is using Drupal.  So I often ask myself, is shared hosting for Drupal really worth the trouble?

I don't know if shared hosting is worth the trouble but a chain of events have brought me to giving shared hosting another chance for my Drupal sites.  Last month, I pushed my VPS so close to the bleeding edge that it became unstable.  While I was able to get my sites back online, the downtime clearly told me it was time to move my sites to a new server.  While most visitors observed a performance improvement  for my Drupal sites since the server migration, it's only now that I'm letting the cat out of the bag.  For the past week, CMSReport.com has been under a shared hosting plan and not a VPS.   I'm currently running my site using a budget shared hosting plan through my reseller site which is comparable to the hosting plans offered by GoDaddy.

I don't know how long I'll keep my site on a shared hosting plan but I am currently enjoying a break from the work, worry, and experimentation that comes with administration of a VPS.  While I may go back to a VPS, I thought it would benefit some newbies and other Drupal users my experiences and thoughts on migrating my sites from a VPS back to a shared hosting plan.

What seems like a very long time since I first heard about and ordered the new Drupal book, Pro Drupal Development, it finally arrived at my doorstep. So far, I have only read Chapter 1, "How Drupal Works", and glanced at the remaining pages of the book but I'm very impressed. The book is written in a very easy, well organized, and informative writing style.

Dries Buytaert had mentioned that when the Drupal developers came together at the Open Source CMS Summit he hoped they could make a video using Jeff Robbin's catchy Drupal Song.  I'm not sure the status of that video by the developers, but as a fan of Drupal I decided to beat them to the punch.

My son and I have become addicted to The Drupal Song.  In fact, when the song is playing in my house we quickly become The Drupal Boys.

The Newbie Issue

I received an interesting e-mail the other day through the contact form at my site regarding the social bookmarking "features" I have for my posts.  The questions asked to me are quite common among new users of any Web content management system.  While the questions in this particular e-mail I received would be more appropriate to be asked and answered in the forums at Drupal.org, there were some things in the message I felt the need to address though my blog.

The first e-mail went like this:

On a recent visit to Drupal's forum I found another post with both Joomla and Drupal in the subject line. Making comparisons between Joomla and Drupal are very common these days as they are currently considered the top two open source content management systems (CMS) out there. The forum post written by Steve Burge contains a link that takes you to a comparison table he did between Joomla and Drupal.

Last night, I was up late doing some administrative work for my sites as well as writing some posts. This was my attempt to procrastinate working on an osCommerce site that I promised someone would be done by the start of October.

One of those posts I made was Drupal related and available via an RSS feed for Planet Drupal to ingest. Unfortunately, I found that TinyMCE (a WYSIWYG editor) had changed my absolute links to relative links in the post. This caused references to links and images back to my site to not display properly for anyone aggregating from the RSS feed I provide. This particular issue with TinyMCE and associated Drupal module is not so much of a bug as it is a configuration issue that can easily be corrected.