Drupal 7: Ready for the Plunge?

[[{“type”:”media”,”view_mode”:”media_large”,”fid”:”740″,”attributes”:{“class”:”media-image size-medium wp-image-1493″,”typeof”:”foaf:Image”,”style”:””,”width”:”300″,”height”:”200″,”title”:”Drupal”,”alt”:”Ready to jump into Drupal 7″}}]]

Ready to jump into Drupal 7

One of the least exciting things to hear when you start on a new web project is, “Not yet.”

That’s just what we’ve been saying since Drupal 7 debuted in January 2011. True, it’s a robust and powerful system with excellent accessibility, and we’re using it for a few of our clients now, but not everybody.

Why not jump in? First of all, it’s not quite ready for everyone. Contributors to Drupal 7 are still busy finding and patching bugs and upgrading the features from earlier versions so they work on this new version.

Secondly, it can be a heavy expense. Upgrading from an earlier version of Drupal isn’t simply downloading a patch and refreshing your screen. It’s a whole new website. Any new website takes time to build, not even including moving over all the content (words and images) and testing. Time and complexity equal money, and an organization needs to have a strong case for upgrading before making that decision.

One exception is if you’re using a very old version of Drupal, such as version 5 or earlier. The Drupal community stopped supporting and patching version 5 last year, so they’re vulnerable to security breaches and should be updated as soon as possible.

Our advice? Absolutely pull on your swimsuit, but check with your developer (or just contact us) before plunging into an upgrade.

Scroll to Top