4 ms·
The biggest gripe I've had with Drupal was when moving from 6 to 7, they had module writers pledge that their modules would be ready on the release day of 7, wh
by johnatwork 11y ago
The biggest gripe I've had with Drupal was when moving from 6 to 7, they had module writers pledge that their modules would be ready on the release day of 7, which a lot of folks broke the promise or worse, abandoned the project all together without letting anyone know.
So some folks were caught not being able to upgrade due to a crucial module being abandoned at 6.
- SwellJoe 11y agoI have that problem, as well. But, the biggest problem I have is that even when there was a pledge to do so and when they actually eventually produced a D7 module (Drupal 7 is several years old...I spent most of this time waiting for the modules we rely on to become stable on Drupal 7), there wasn't a pledge to provide an upgrade path...so, you've got data in some module in Drupal 6, and no way to get that data into the same module in Drupal 7. Often there are bizarre workarounds, like using the Migrate module, which is designed to handle all sorts of migration tasks and is thus endlessly complex, and requires custom migration code (and comprehension of a huge swath of even more new jargon and convoluted, baroque, APIs). It begins to remind me of Zope/Plone from many years ago, which had many of the same problems. Lots of jargon, lots of new ideas in each version before the old ideas were stable or fully implemented, painful upgrades, tight coupling of interfaces making changes in one part of the system require changes in every part of the system. A modular system is nearly meaningless, if every module has to be rewritten with every new release.