Upgrade readiness
This checklist is for the site administrator and project manager of a public body planning an upgrade within the 6.0.x line. The steps come from Update with Git, Upgrading and The upgrade check.
Contents
Before
- To do: Current version noted from Setup > System information (System information).
- To do: Changelog of every version you pass read, and the upgrade notes it links (6.0.15 changelog, Upgrading, Part C).
- To do: Setup > Upgrade check run: files changed in place found and moved into extensions or overrides (The upgrade check).
- To do: Your own extensions checked against the changes (Upgrading, C4).
- To do: The upgrade rehearsed on a staging copy with a written test list.
- To do: A maintenance window agreed and announced.
- To do: A fresh backup of database and files (Backup readiness).
During
- To do: Maintenance mode on, administrators allowed (Maintenance mode).
- To do: The seven steps followed, by command line or administration (Update with Git):
- To do: update the kernel (Git, or Git Manager);
- To do: update the extensions (Composer, or Setup > Updates and packages);
- To do: check and update the database;
- To do: clear the caches and reload the code (for example
php bin/php/ezcache.php --clear-all --allow-root-user, then reload the engine) (Caches);
- To do: Checked as administrator before visitors return.
- To do: Maintenance mode off.
After
- To do: Setup > System information shows the new version and no open health checks.
- To do: Key journeys tested: home page, search, a form, sign-in, publishing an article, a download.
- To do: Setup > Log files checked for new errors (Log viewer).
- To do: Accessibility spot check on the main templates.
- To do: Editors told what changed in the administration; training material updated.
- To do: The upgrade recorded: from, to, date, who, issues.
Upgrades from older lines
A site on 5.x, 4.x or the Symfony platforms is not supported and needs a migration project, not a routine update (Supported versions):
- To do: Read 14. Migrating from the 4.x line, 15. Migrating from the 5.x legacy stack or 16. Migrating from eZ Platform and Ibexa.
- To do: Use the Migration checklist.
- To do: Budget it as a project (Planning upgrades in the budget).
Related pages
- Government checklists
- Upgrading customer sites (for hosts)
- Updates and upgrades (for site builders)
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.