Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My website runs on Drupal 7 and I hear it is no longer supported

Short answer

Drupal.org announced that once Drupal 7 reaches end of life, the Drupal Security Team stops issuing security advisories for it, its modules and themes, security issues may be disclosed in public, and scanners will flag it as insecure. Drupal.org recommends moving to a current version. Your site does not stop, it just stops being patched.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My developer told me Drupal 7 is end of life and I should do something.
  • A security scan or my hosting company flags my site as using unsupported software.
  • Nobody has updated the site for a long time and it still works.
  • I do not know whether to upgrade, rebuild or move to something else.
  • My site has custom modules and I am afraid to touch it.

Why does this happen?

  1. Security advisories stop

    Drupal.org says that after end of life the Drupal Security Team no longer provides support or Security Advisories for Drupal 7 core, contributed modules or themes, and that there are no more core commits on Drupal 7.x.

  2. Problems may become public

    The same announcement warns that security issues for Drupal 7 may be disclosed in public and that zero-day vulnerabilities may occur. A known weakness with no official fix is the usual way old sites get hacked.

  3. Tools and downloads change

    Drupal.org says all Drupal 7-compatible releases on project pages will be flagged as not supported, some Drush functionality for Drupal 7 will stop working, and external vulnerability scans will flag Drupal 7 as insecure.

  4. There is no in-place upgrade

    Drupal's upgrade guide treats a legacy Drupal 6 or 7 site as a migration, not an update. It has separate pages on preparation, choosing an approach and known issues, so the move is a project with its own planning.

What can I do about it today?

  1. Do not switch the site offEnd of life does not stop the site working. Taking it down loses visitors and orders for no gain.
  2. Confirm the versionAsk your developer or host to confirm in writing which Drupal version and which PHP version the site runs on.
  3. Make sure a backup existsAsk for a recent copy of the files and the database, and ask where it is stored and who can restore it.
  4. List the admin loginsAsk who has an administrator account. Remove the ones for people who have left, but only through the site's own user list, and only after a backup.
  5. Write down what the site does for youForms, member areas, shop, integrations. This list decides whether you migrate, rebuild or simplify.
  6. Do not install update modules yourselfA change made on a site nobody has tested can bring it down. Leave changes to someone who has a backup and a way back.

When should I bring someone in?

  • The site takes payments, holds member data or is a main source of enquiries.
  • A scan has flagged the site, or you see pages or links you did not create.
  • You are unsure whether your developer still has access to the site.

How do I handle it?

  1. Audit before choosingI list the modules, themes, custom code, content types and integrations, and mark what is used, unused and unsupported.
  2. Offer the routes honestlyMigrating to a current Drupal, rebuilding on another platform, or simplifying to a smaller site: each with what it keeps and what it costs in effort, in writing.
  3. Reduce risk while you decideA backup is taken first, access is cleaned up and unused modules are listed for removal, one change at a time, with a tested way back.
  4. Migrate on a copyContent and users are moved to a new site that is checked side by side with the old one before any address changes.
  5. Switch with redirectsOld addresses point to new pages and the old site stays available until the new one has proved itself.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will my Drupal 7 site stop working?

The announcement does not say the site stops. It says Drupal.org stops supporting Drupal 7 and its security team stops issuing advisories, so the software is no longer patched.

What does Drupal.org recommend?

Its announcement recommends that people running Drupal 7 migrate to Drupal 10.

Can I update Drupal 7 to a newer version like a plugin?

Drupal's upgrade guide describes Drupal 6 and 7 sites as being upgraded through migration rather than an in-place update.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.