Drupal 7 Will Reach End-of-Life in November of 2021 (drupal.org)
Drupal 7, which was first released in January 2011, will reach end of life (EOL) in November of 2021, the Drupal Association said today. What this means for your Drupal 7 sites is, as of November 2021: 1. Drupal 7 will no longer be supported by the community at large. The community at large will no longer create new projects, fix bugs in existing projects, write documentation, etc. around Drupal 7.
2. There will be no more core commits to Drupal 7.
3. The Drupal Security Team will no longer provide support or Security Advisories for Drupal 7 core or contributed modules, themes, or other projects. Reports about Drupal 7 vulnerabilities might become public creating 0 day exploits.
4. All Drupal 7 releases on all project pages will be flagged as not supported. Maintainers can change that flag if they desire to.
5. On Drupal 7 sites with the update status module, Drupal Core will show up as unsupported.
6. After November 2021, using Drupal 7 may be flagged as insecure in 3rd party scans as it no longer gets support.
7. Best practice is to not use unsupported software, it would not be advisable to continue to build new Drupal 7 sites.
8. Now is the time to start planning your migration to Drupal 8.
2. There will be no more core commits to Drupal 7.
3. The Drupal Security Team will no longer provide support or Security Advisories for Drupal 7 core or contributed modules, themes, or other projects. Reports about Drupal 7 vulnerabilities might become public creating 0 day exploits.
4. All Drupal 7 releases on all project pages will be flagged as not supported. Maintainers can change that flag if they desire to.
5. On Drupal 7 sites with the update status module, Drupal Core will show up as unsupported.
6. After November 2021, using Drupal 7 may be flagged as insecure in 3rd party scans as it no longer gets support.
7. Best practice is to not use unsupported software, it would not be advisable to continue to build new Drupal 7 sites.
8. Now is the time to start planning your migration to Drupal 8.
EOL the whole project, in fact.
During your move to Drupal 8 - certainly don't admit to holding any views contrary to Drupal's "community" norms. And if you threaten Dries IPO prospects in ANY way, watch the Drupal org break all of their stated principles to burn you.
I've tried to migrate my site to D8, and the body content isn't displayed, and nobody on the forum responded at all. What a PITA. Guess I should get on that a bit more.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
I haven't even thought about in months... I mean I'm glad people are choosing something that isn't the steaming pile of U+1F4A9 that is WordPress, but...
Isn't it time for something new? Better? Perhaps not written in PHP? Perhaps written by actual software developers and not web designers who need someplace to sell their themes?
and I for one would like to welcome our new resurrected Drupal overlord called Backdrop CMS
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
Drupal 7 runs on php7.2.
It does require money and time to do security analysis on old code. That is a fact of life. They're looking at migrating to Drupal 9 down the road, and 7 will be EOL'd. They're giving a long time duration warning for when EOL will happen.
That said, I haven't looked to see how many Drupal 7 modules haven't yet or won't be ported to Drupal 8. The module support is Drupal's Achilles heel if anything. The core isn't awful to move from release to release. But when large numbers of add-on modules are unsupported in the next release because the Drupal developers have changed things in annoying ways (even if for perfectly good reasons) it makes it tough to upgrade end user websites if there is no comparable functionality. You either drop those features or hope for the best, or if the functionality has been merged with core, you do a big database alteration to try to get the old functionality with the new core. With the number of severe security holes in 8 and 7 lately, hoping for the best isn't a good plan.
According to the makefiles in https://bitbucket.org/account/user/drupalorg-infrastructure/projects/PROJ, drupal.org is itself still using Drupal 7. Despite Drupal 8.0.0 being released in November 2015. I won't feel comfortable migrating my Drupal 7 site to Drupal 8 until the Drupal.org infrastructure team is confident enough in the 8.x branch to eat their own dogfood.
Meanwhile, groups.drupal.org appears to be using a patched version of Drupal 6, which went EOL in February 2016.
Is the November 2021 Drupal 7 EOL going to be a "Hard Drexit" or a "Soft Drexit"?
CAPTCHA: taking
Perhaps they should spend some time to migrate drupal.org off of Drupal 7.63
Why would you upgrade to 8 if the creators of it won't upgrade their own site?
No it is not!
There are migration scripts available but your mileage may vary especially if you wrote custom stuff. Third party modules may also be a concern.
https://www.drupal.org/docs/8/...
Everything I write is lies, read between the lines.
Does that mean I can't catch season 6 of Drupal's drag race on Netflix?
-- Political fascism requires a Fuhrer.
How straightforward is the migration path?
My previous experience of Drupal (a long time ag) was that it was easy to setup a gorgeous site, but that making it is update-prone was not a layman's job. Odds were good that it would need a complete reimplementation.
I have several web sites running Drupal 7. The biggest issue that prevents me from migrating to Drupal 8 is the status of several contributed modules that I depend on. If they don't have a Drupal 8 version available (and there are many that don't), I have to either update them myself or find an alternative. The most common reaction I get from the developers of these modules when asked about their plans for Drupal 8 is silence...