Updating from <2.5¶
If you are updating from a version prior to 2.4, you have 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
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:
bin/console cache:pool:clear cache.redis