

What's more, your developer team knows Drupal 7 like the back of their collective hand. If everyone is already well-practiced in using it, it's invaluable.īut what if you have ten years of business logic built into Drupal 7? It represents thousands and thousands of hours and millions of dollars of total investment. Having a ubiquitous language makes everything easier. If your team is already comfortable communicating with Drupal's vocabulary, that is one less thing you have to worry about. This might seem small, but it's a bigger deal than you might think. Entities, nodes, view modes, themes, modules, taxonomy, fields, etc. A lot of the vocabulary will still be the same. Ever since Drupal 8, new versions of Drupal have left Drupal 7 behind, and a lot of your institutional knowledge will not transfer one-to-one. However, you really are getting a completely new system. An extensive library of ready-to-use open source modulesĪnd this is important to understand: You can skip Drupal 8 and jump straight to Drupal 10.A global security team helping to protect your investment.Robust and extensible system for handling translations.More frequent minor releases and easier updates.You'll have a modern CMS that measures up to any other option you could choose. And there is a lot you can do to prepare your Drupal 7 website for that eventual migration.ĭrupal 10 and above will give you the latest and greatest that Drupal has to offer. There are a lot of good tools you can use to help you migrate to the latest version of Drupal. You have decided you need to move off of Drupal 7. In other words, the cost to simply "keep the lights on" goes up with every passing day.

Or making sure it still works with your database.

Or making sure it stays up to date with new operating systems. Or making sure it stays compatible with newer versions of PHP. The cost of moving off of Drupal 7 might seem high, but it will be less than the cost of trying to recover from an undiscovered Drupal 7 security exploit after its final EOL. Consider this final EOL extension an extra hour of daylight to help you get your affairs in order. The problem is that your steed is old and might collapse at any moment, and now the sun is down, and it will be much harder to secure a new one.īetter to let Drupal 7 retire while the sun is still high and clear in the sky and you still have daylight to secure your next solution. You might try to ride Drupal 7 off into the sunset, trusting your noble steed for one more adventure. So are you going to stay on Drupal 7? The answer, at some point, will need to be a resounding "no." Drupal 7 lives, but it lives only to die another day. Drupal 7 has some simple, rudimentary API support, but if you want a full-fledged API with write support, you'll need to create it yourself, which adds additional technical debt and potential vulnerabilities. In the age of "publish everywhere," this is important functionality.
Drupal security release date update#
You can mitigate this a little bit with the jQuery Update module, but the highest version you will get is 2.1.x.ĭrupal 8 and above (and many other content management systems) have easy ways to enable API access to your content. The other libraries are in similar situations. Out of the box, Drupal 7 comes with versions of these libraries that are obsolete and unsupported. Not just with Drupal, but with your entire web stack.įor example, Drupal 7 depends upon several JQuery libraries: You are missing out on the new features and performance enhancements you would get with more recent technology. But it will end.Īnd in the meantime, anyone still on Drupal 7 is paying a high opportunity cost.
Drupal security release date software#
In dog years, it's 70 years old, and in software years (something we just made up), it's even older than that.ĭrupal 7 has served us well, but like all good things, it must come to an end. While a decade doesn't seem like a long time when you compare it to the age of the universe, ten years is a long time for software to stick around. If the answer to this question is "yes," there are some things you should know.ĭrupal 7 is over eleven years old. There are two questions you should start asking. You have some important decisions to make, and once you make them, you need enough time to execute those decisions. But don't use the next year and a half to lounge about and twiddle your thumbs. If you are still on Drupal 7, you have some breathing room. Drupal 7 will reach end of life on January 5th, 2025.
