Drupal Disappointment

I’m becoming very disappointed with Drupal, due to version 6’s lack of backward compatibility. A lot of very basic modules still haven’t been upgraded to work with Drupal 6, yet they’re already working on Drupal 7. I still haven’t upgraded any of my sites to Drupal 6 and I probably won’t upgrade them. I doubt if I’ll be able to upgrade to version 7 either, without first upgrading to 6.

Corey Smith wrote about moving from WordPress to Drupal, but I’m thinking of going the opposite way. Daniel first brought up the idea of moving MacMegasite to WordPress, which I discounted at first because it would lose a lot of functionality.

I would be losing the forums, buddy lists, the point system, and some of the less-used features like feed aggregators & user blogs. Some of these features could be implemented with WordPress plugins and a separate forum system. The most critical feature is the ability to have multiple authors, which WordPress supports.

On the plus side, WordPress is a lot more attractive, with more professional looking themes, and a much nicer content entry screen. I’m concerned that WordPress seems to use more GPU according to MediaTemple’s GPU usage report. My Drupal sites use anywhere from 0.0005 to 0.0014 GPUs per hit, while this site uses 0.0017 or more GPUs per hit. It may be a due to the plugin configuration.

I’ve seen a few articles about moving from Drupal to WordPress, so I know it’s been done. It would be a big project, so I probably won’t do it until after I finish my current projects and release the iPhone apps I’m working on.

2 thoughts on “Drupal Disappointment”

  1. I’ve recently ported a couple of modules from Drupal 5 to 6, and it was pretty painless on the whole. Some are going to be insanely hard, of course.

    Yes, I was also disappointed at how long it took for Drupal 6 modules to become common. I think everyone was waiting for everyone else. Hopefully people have learned their lessons now and it won’t be so bad in Drupal 7.

    Reply

Leave a Comment