4 ms·

I spent some time with Drupal a while back and stubbed my toe on each of these points. My favourite pet peeve was the fact that Drupal was repeatedly upgraded

I spent some time with Drupal a while back and stubbed my toe on each of these points. My favourite pet peeve was the fact that Drupal was repeatedly upgraded in a manner that broke existing sites, and required users to do hairy manual SQL and theme changes. If you're marketing a CMS to a not-so-sophisticated audience (which is basically who CMSes are aimed at), then an essential part of the upgrade process is the creation of tools to perform the upgrade without having the entire site in pieces on the garage floor.

aasarava 17y ago
Out of curiosity, how long ago was "a while back"? I've been building on Drupal since version 4.7 (now on 6.14) and haven't ever had a problem with sites breaking on upgrades within major versions. It's only when upgrading from v4 to v5 to v6 that I've had to adjust my custom templates and modules to work with new APIs. But that's why major upgrades get new major version numbers and are years in the making (and testing).