Weekend at Drupal 7's: Still Partying Past EOL
summary
Claims that thousands of Drupal 7 sites still run after final EOL on January 5, 2025 — about 259,000 sites by update-module counts — and HeroDevs ships a forked Drupal 7 core with an NES (Never Ending Support) module that replaces the update module, connects to an API, and issues security and PHP 8.3 compatibility patches. Service runs on annual tiers (basic vs certified SLA), typical fix turnaround under 72 hours (14-day guarantee), is a drop-in replacement that doesn’t handle backups but keeps legacy sites compliant.
AI-written summary · about
chapters (10)
- 0:00Welcome and introduction
- 0:46Why Drupal 7 still runs
- 3:58Reasons to stay on Drupal 7
- 5:23Timeline of Drupal 7 EOL delays
- 6:27Security risks after EOL
- 7:31Maintenance strategies for Drupal 7
- 9:17Three-step security routine
- 10:00Security patches and compatibility
- 11:25Open floor for questions
- 18:16Budget and migration challenges
