Older releases of this kernel
Exponential 6 is the continuation of the eZ Publish legacy kernel, a product its creator discontinued after almost 18 years. Sites that still run one of its releases move to Exponential 6 in place: the database is updated by the update files of this repository, the code is replaced, and the extensions are ported to PHP 8. Nothing has to be exported and imported. The old name appears below only to identify the release you migrate from.
Which release do you run?
Read lib/version.php of the old installation and the version rows of ezsite_data
(chapter 11.2); for the 5.x era, look at the installation root
(chapter 15.2).
| You run | Guide | The database path |
|---|---|---|
| 3.0 to 3.9 | Chapter 14.5.1 | not directly: the update scripts of those versions are not in this repository; bring the site to 3.10 with the old 3.10 release first, then follow the next row |
| 3.10, 4.0 to 4.7 on PHP 5 | Chapter 14 | the old chain to 5.4, then to 6.0.0, then to today |
| 5.0 to 5.4, community 2013.x and 2014.x (with the Symfony stack) | Chapter 15 | extract the legacy part; the 5.4 database goes to 6.0.0, then to today |
The 5.90 legacy-only line (2015.01, 2017.08, 2017.12 and later releases that report VERSION_MAJOR = 5, VERSION_MINOR = 90) | Chapter 11.5, with 15.9 for passwords | to 6.0.0, then to today |
| Releases named after a year later than 2017 | not verified in this repository | read lib/version.php: a 5.90 release follows the row above |
| LoveStack (Mugo Web's distribution of the legacy kernel) | LoveStack: migration | ./console exp:explovestack checks it and records its database as Exponential's |
| Exponential 6.0.0 to 6.0.14 | Chapter 11.6 | the 6.0.x update files |
Then chapter 17 has the lookup tables, and chapter 12 the fixes for what goes wrong.
The steps every older release shares
- Copy, never in place. Restore a backup of the old site on a staging server and migrate the copy.
- Preflight: charset and table type (MySQL), the preflight queries of 14.5.3.
- Phase A: every SQL update file of the chain, in order (14.5.5).
- Phase B: the PHP repair scripts, against the finished schema (14.5.6).
- Code: a fresh Exponential 6 (chapter 3); settings, designs and extensions carried over; extensions ported to PHP 8 (14.9).
- Verify (14.12), rehearse, cut over; keep the old site until sign-off (14.14).
The addresses of an in-place migration stay the same (the URL alias tables move with the database), so redirects are needed only for what you change on purpose.
Moving on from there
Once the site runs on Exponential 6, every other path of the hub is open: the Symfony stack next to it (Platform Legacy), a page-building distribution (Nexus), or a Symfony-only platform (DXP). Do one move at a time.
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.
This page is part of the Exponential documentation and is free documentation under the GNU Free Documentation License 1.3 or any later version (the license of this documentation).