With version 8, Drupal introduced some radical changes and was basically a re-write of Drupal code, this means that Drupal versions from 8 upwards do not bear much resemblance to Drupal 7 in terms of the underlying system and therefore it is not possible to simply upgrade from Drupal 7 to a later version, instead your website must be migrated to Drupal 10. ![]() Migrate to Drupal 10ĭrupal 10 is an excellent system with many improvements and is an extremely powerful and future-proof platform, but there are some considerations to bear in mind when moving to Drupal 10. The reality is that for most businesses and organisations, their website is an important asset and even the risk of it going down for a prolonged period of time, or being defaced in some way (no matter how small the chance may be), is just not an acceptable risk. 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. 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).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |