3 ms·
I don't understand this comment. You left because the updates were frequently required? Or because some aspect of applying the updates was difficult?
by snowwrestler 11y ago
I don't understand this comment. You left because the updates were frequently required? Or because some aspect of applying the updates was difficult?
- debacle 11y agoThe nature of the application means that any sort of semi-complicated update has to be applied manually to some degree. Think of a database, but instead of a database you have some weird mix of MS Access and irresponsible use of EAV. That's Drupal.
- minsight 11y agoWell put. Also, the developers (at least when I was involved with it) had a thing for repeatedly changing internals such that new developments (most importantly, security-related developments) required orders of magnitude more ability in a variety of esoterica than the install process did.
- minsight 11y agoThe application of updates required manually updating databases. There was an easy-to-use installation procedure but the upgrade process was both not automated and very easy to break. The developers (at least at the time) were more interested in making repeated breaking changes than they were in investing the effort to allow earlier adopters a reliable upgrade process. My irritation was that this was the metaphorical equivalent of a business offering a fantastic deal to new customers but treating existing customers with palpable disdain.
- ajsalminen 11y agoWhat kind of manual steps are you talking about? Updating Drupal is usually fairly straightforward and unless you're talking about an alpha/beta release or doing a major version upgrade and definitely doesn't require manual database changes most of the time.