![drupal 7 end of life drupal 7 end of life](https://www.commonplaces.com/hs-fs/hubfs/Screen_Shot_2016-01-26_at_3.10.07_PM-1.png)
#DRUPAL 7 END OF LIFE CODE#
Indeed, some of these risks can be so critical that you end up rewriting large chunks of code to deal with them. If you do hire someone, that person won’t be as familiar with the project as one of the maintainers would be, so you’d have to factor in that additional investment. This forces you to either live with them or to fix them, or again, hire an agency to do it. Functionality RisksĪs the Drupal community continues to diminish the amount of activity on Drupal 7 core and contributed modules, especially after end-of-life, you basically lose those “free” updates.
![drupal 7 end of life drupal 7 end of life](https://www.arcstone.com/hs-fs/hubfs/drupal-end-of-life.jpg)
#DRUPAL 7 END OF LIFE UPDATE#
Because the Drupal module that connects to it is no longer being actively maintained, you (or an agency you hire) will have to update the module or write a new custom module to keep integration working. For example, your Drupal environment may be integrated with another platform, and a key API on that platform is getting deprecated. Integration RisksĬertainly, security risks will come along, but another risk area in maintaining the status quo is that key integrations will eventually start to fail. Drupal 9 has additional advantages such as support for PHP 8.0. In this blog post, Peter Wolanin of Acquia details some significant security improvements included in the initial Drupal 8 release.
#DRUPAL 7 END OF LIFE UPGRADE#
In the history of previous Drupal security fixes, some have been pretty small - one-line changes that take an hour to review and fix - while others have taken days or even weeks of development time to analyze and produce a solution for.Īn advantage of choosing to upgrade a Drupal 7 site to Drupal 9 is that you gain all of the advantages of security improvements that were included in Drupal 8 and each subsequent feature upgrade. For a good many developers, this is not rewarding work. Every aspect of a Drupal application must be considered to ensure there are no security gaps.Īnother aspect of taking this path is that much of the time maintaining a site like this is spent managing and mitigating security risks rather than making improvements or implementing new features. As a point of reference, after Drupal 6 had reached its end of life, there weren't a disproportionate amount of security fixes needed for its core nor contributed modules. These fixes will of course not be included in the D7 upgrade path because there won’t be an upgrade path at all. One of their main tasks is to backport fixes for core and contrib issues.
![drupal 7 end of life drupal 7 end of life](https://www.raghwendra.com/blog/wp-content/uploads/2018/09/drupal-7-8-and-9-versions-1.jpg)
This will help greatly to secure your site if you’re willing to invest in hiring such an agency. There will be a few agencies that will offer the service of maintaining your Drupal 7 platform post end-of-life. This risk gets compounded if there are a lot of contributed modules in your Drupal configuration. Site maintainers could find themselves in the position of having to spend a lot of time searching for security holes and fixing them. Security RisksĪfter Drupal 7 reaches the end of life, whenever security issues are identified in core or contributed modules, there won't be very much support to fix them. There are three general areas of risk: security, integrations, and functionality. What we can do, however, is make organizations that use Drupal aware of the risks of not upgrading. However, in the case of future security threats, we can’t be confident of what the future ongoing costs will be, because we can’t predict when such security threats will arise, nor will we know the severity of them. The business case exercise can further forecast the break-even point for your upgrade investment. maintaining the status quo, as well as projections for revenue and savings. If your organization is currently running Drupal 7, you’re faced with a decision on whether to upgrade to Drupal 9 or not.Ĭrafting a business case can help with your decision because it contains projections for initial costs and ongoing costs for making the upgrade investment vs. After that point, however, the Drupal Security team will no longer support Drupal 7. Up until then, the Drupal Security Team will continue to provide patches to Drupal 7 core and contributed projects should any security threats arise. Drupal 7's end of life is scheduled for November 28, 2022.