MultiCmsManager

Drupal 9

Drupal 9 has reached end of life: monitoring and the move to Drupal 10

Drupal 9 went out of support on 1 November 2023, together with Symfony 4. About one Drupal site in ten is still there, almost always on 9.5.

The problem

The last step to Drupal 10 is the costly one.

Drupal 10 needs PHP 8.1, drops some modules and themes from core and needs new versions of many contributed modules.

Meanwhile the site stays on a core that gets no fixes.

How it works

Watch, back up, upgrade.

  1. 1

    Checks

    End-of-life alert, modules on insecure releases, core integrity and suspicious files.

  2. 2

    Backup

    A full encrypted backup before touching Composer.

  3. 3

    Upgrade

    Real move from 9.5 to 10.0 with Composer and drush updatedb: one notification, core identical to the 10.0 archive.

In detail

What we saw in testing.

  • Drupal 9.5 with PHP 8.1, which is also the Drupal 10 minimum
  • After the move, drupal.org marks 10.0.11 as insecure: the alert tells you to continue to 10.6
  • We also tested the next steps, 10.0 to 10.6 and 10.6 to 11.3

FAQ

Frequently asked questions

Does the module stay connected during the upgrade?

Yes. It is the same module for Drupal 9, 10 and 11 and does not need reinstalling.

Which Drush did you use?

Drush 12 for Drupal 10. On Drupal 9 with PHP 7.3 you need Drush 10, because Drush 11 requires PHP 7.4.

Try it on your clients' sites.

During the beta we let in a few agencies at a time and set up the first sites with you.