![]() What other options are there?įor very small businesses or organisations, or for someone who isn’t interested in developing their website or doesn’t believe it’s a key asset to their business, they may decide to just run past January 2025 without doing anything and not worry about it unless something happens. If its an acceptable risk for your website to possibly go down at some stage in the future, or less likely, be defaced in some way, and you will just have a new website built when or if that time comes, then yes, it’s an option. So, if you have a basic Drupal 7 website that meets the description above, is it really an option just to leave it running past end of life without further support? The answer is yes, despite the fact that everyone in the Drupal community would advise against this. In reality the vast majority of attacks are automated. However, a hacker generally wants some kind of reward, and if there’s nothing of value to steal on your website its fairly unlikely they are going to bother defacing your website unless you are being specifically targeted. The worst you could expect is for your website to go offline, or for it to potentially be defaced in some way by a hacker, which of course could harm your reputation. If your website does not contain any sensitive data (like ecommerce transactions), does not hold personal data on users, is not integrated with any 3rd party systems, and does not allow users to log in, then the risks are fairly minimal. The risks of running a Drupal 7 website past end of life without further support will largely depend on what your website does, how it works, and what data it contains. ![]() It means your website is more likely to be hacked and it means your website will eventually start displaying errors or stop working completely after some time, simply due to becoming too old to keep up with modern web technologies. Reports about Drupal 7 vulnerabilities might become public creating 0-day exploits. The Drupal Security Team will no longer provide support or Security Advisories for Drupal 7 core or contributed modules, themes, or other projects. It means that updates, security fixes, and enhancements will no longer be provided by the community. The Drupal community and the Drupal security team will stop supporting Drupal 7 in January 2025, but what does this mean in practical terms? Your Drupal 7 website is not going to suddenly stop working, nor is it going to suddenly come under attack. When January 2025 arrives what exactly will happen? Well on the face of it, very little. We do offer Drupal 7 services and we will provide a link later, but this post is about what option is right for you specifically and that may mean not availing of our services, or indeed anyone’s services possibly. This is an honest and straight-forward perspective on what options you have. As maintainers of several contributed projects such as Protected Submissions, Search Index Options, Sticky Note, AltaGrade team will continue supporting them all until Drupal 7 reaches end-of-life on November 28, 2022.Update - This article has been updated to reflect the recent announcement that the Drupal 7 EOL has been extended to January 2025.ĭrupal 7 was first released in January 2011 and In January 2025, after well over a decade, Drupal 7 will reach end of life (EOL). The Drupal Security Team will continue to follow the Security Team processes for contributed projects. You can read more about the Drupal 7 Vendor Extended Support program. The extended support will now run from November 2022 until November 2025. What about Drupal 7 Vendor Extended Support? ![]() Read more on preparing a Drupal 7 site for Drupal 9. Migrating directly from Drupal 7 to Drupal 9 is supported with the core Migrate module. Do I need to upgrade to Drupal 8 before I upgrade to Drupal 9? This will give you an extra year to work on converting your site to Drupal 9 or Backdrop. You can continue to run the site and get security updates via the normal channels and processes. What does this mean for my Drupal 7 site? ![]() It definitely seems unusual that Drupal 8's support is going to end sooner than Drupal 7 reaches its end-of-life, however since the upgrade path from Drupal 8 to Drupal 9 is much easier, the impact is predicted to be comparatively less. ![]() The Drupal Security Team has announced today that given the impact of COVID-19 on budgets and businesses Drupal 7's end-of-life, previously scheduled for November 2021, will be extended until November 28, 2022.Īt the same time, it's noted that Drupal 8 will still reach its end-of-life on Novemdue to Symfony 3's end of life. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |