Slashdot Mirror
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.
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.
Which one would be better: EOL Drupal or EOL WordPress?
Let's say you can only ban one from the internet.
#DeleteFacebook
ExpressionEngine 5 is now open source. Seeing some of their (stupid/dumb) design decisions, I'd say these guys have more of a database background than a web designer background.
#DeleteFacebook
Which one would be better: EOL Drupal or EOL WordPress?
Let's say you can only ban one from the internet.
It has to be WordPress. Drupal is far from perfect, but WP is even farther.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
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.
Moot. They're both equally fucked.
I suggest not to listen to strangers on the internet ranting about something from their boycave, and just use what fits your needs best.
Yes i dislike WP too. And drupal too. Any CMS really. But when i have to make a website for the boss, i just pull one of them of the shelve and get the job done. Preferably one that's still supported in 5 year, depending on the site. Anything mission-critical is not made with such CMS anyways, it serves another purpose and another market and pretty much any of them does what it needs to do. Just like your smartphone - when was the last time you seriously cared about the brand of phone as long it worked?
A glitch a day keeps the bugs away.
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.