Updating from <2.5¶
If you are updating from a version prior to 2.4, you have to implement all the changes from Updating from <2.4 before following the steps below.
During database update, you have to go through all the changes between your current version and your final version e.g. during update from v2.2 to v2.5 you have to perform all the steps from: <2.3, <2.4 and <2.5. Only after applying all changes your database will work properly.
Database update script¶
Apply the following database update script:
mysql -u <username> -p <password> <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-7.4.0-to-7.5.0.sql
To update to v2.5.3, additionally run the following script:
mysql -u <username> -p <password> <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-7.5.2-to-7.5.3.sql
To update to v2.5.6, additionally run the following script:
mysql -u <username> -p <password> <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-7.5.4-to-7.5.5.sql
or for PostgreSQL:
psql <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/postgres/dbupdate-7.5.4-to-7.5.5.sql
To update to v2.5.9, additionally run the following script:
mysql -u <username> -p <password> <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-7.5.6-to-7.5.7.sql
or for PostgreSQL:
psql <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/postgres/dbupdate-7.5.6-to-7.5.7.sql
Additionally, reindex the content:
Changes to database schema¶
The introduction of support for PostgreSQL includes a change in the way database schema is generated.
If you are updating your application according to the usual procedure, no additional actions are required. However, if you do not update your meta-repository, you need to take two additional steps:
Changes to Matrix Field Type¶
To migrate your content from legacy XML format to a new
ezmatrix value use the following command:
Required manual cache clearing if using Redis¶
If you are using Redis as your persistence cache storage you should always clear it manually after an upgrade.
You can do it in two ways, by using
redis-cli and executing the following command:
or by executing the following command:
Updating to 2.5.3¶
This step is only required when updating from versions higher than 2.2 and lower than 2.5.3. In case of versions lower than 2.2, please skip this step or ignore the information that indexes from a script below already exist.
When updating to v2.5.3, you need to run the following script to add missing indexes:
1 2 3 4 5 6 7 8 9
Updating to 2.5.16¶
In order to promote use of eZ Platform,
ezsystems/ez-support-tools v1.0.10, as of eZ Platform v2.5.16, sets the Powered-By header.
It is enabled by default and generates a header like
Powered-By: eZ Platform Enterprise v2.
To omit the version number, use the following configuration:
1 2 3 4
To opt out of the whole feature, disable it with the following configuration:
1 2 3 4