![]() Therefore, let's switch gears and have a look into the third reason why so many Drupal 7 sites haven't updated yet: missing functionality due to not yet updated modules. And I feel sorry for alluding to this, as it may be challenging for many. In other words, not having a budget for a Drupal 7 to 10 update makes me wonder where the budget for the continued use of either outdated, or in the case of switching the platform, less capable technology should come from? While the ongoing effort for running the modern Drupal platform declines immediately, the cost of not upgrading increases exponentially as long as the decision is not being taken. Not only that, the technical debt of our old technology will cause hidden costs over and over again. ![]() ![]() ![]() And that's a good thing because if we didn't progress, we would be falling behind continuously. Not only in this post-Drupal-7 era, but everywhere in life. I'm not saying there isn't another learning curve ahead of us. Having said that, the same infrastructure paradigm-shift is the reason why this composer-based dependency management is often perceived to be complicated. Not only has the Drupal community kept up with an easy upgrade path, their experience helps them to make it even easier for each future generation of Drupal. Drupal has demonstrated this with already 2 major updates from 8 to 9 and then 9 to 10. But from then on, the platform is maintainable and easily upgradable even across major updates for decades to come. In other words, the initial jump might be more challenging. In the context of an upgrade to Drupal 10 that approach misses out on important gains, the composable architecture of the modern Drupal platform in particular. While I can't speak for every individual case out there, what's very common these days is the unfortunate focus on short-term indicators. There is a lot to say about the resource constraints. Missing functionality due to not yet updated modules.Missing resources, either budget or people power.One out of these three reasons is always brought up - sometimes even all of them at once: So, why are so many still holding back on updating to the modern Drupal framework? That's why moving away from Drupal is rarely a great idea. Simply because Drupal is what suits them best. But we know for sure, that hundreds of thousands of Drupal 7 sites haven't moved away from the platform even after that many years. A web presence of any size and purpose benefits from those aspects and many others, this blog post is not about to enumerate them all. While the rich feature set is important to most, the performance, its scalability and security are must-haves not only for enterprise websites. Let's face it, every Drupal site is hosted on that platform for good reasons. Why is the first option certainly the best? That's why there are plenty of discussions in and around the Drupal community of what should be done to all those still existing and mostly deeply necessary Drupal 7 sites. While this had been originally scheduled for a date which has passed for a couple of years already, support got extended and may well be finished in November this year - although that may still get extended again for another year or two. Drupal 7 is going End-of-Life eventually.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |