These instructions take advantage of the Composer powered update systems in 5.3 for maintenance updates, so make sure:
- Familiarize yourself with the Using Composer page.
- Update Composer, as found on Composer self-update documentation
For Upgrading from versions prior to 5.3 look at the Installation and Upgrade Guides.
Before Updating
Follow all* instructions below that applies to the version you're updating from: when updating from 5.3.0 everything applies.
* The version you update to will always be the latests, hence the importance of following all steps.
From 5.3.8 and lower
Update Composer plugins for Composer v1.1
Newer versions of Composer sometimes updates it's API's and as such we need to make sure our composer plugins up-to-date, so to :
From 5.3.2 and lower
Remove Zeta Components packages causing composer conflicts
Issues with Zeta Components and Composer have been fixed (new releases of Zeta Components have been made to fix this) so you should edit composer.json
and remove any "zetacomponents
" package like shown below:
After doing this, verify that content of composer.json
does not contain any entries for zetacomponents/
unless you have your own dependencies on them. ezpublish-kernel
and ezpublish-legacy
now always requires the specific versions of the Zeta Components we use internally.
Update your Nginx configuration
If you're using Nginx as your webserver instead of Apache, then make sure to update Nginx vhost configuration, changes since 5.3.0: 5.3.1, 5.3.3
From 5.3.3 and lower
Optional: Change composer.json to avoid occasional fatal error on asset dump when performing composer update
For issue EZP-23492 - Improve use of assetic dump with composer Closed composer.json should be edited to take full advantage of the improvement, see the following commit for patch.
From 5.3.4 and lower
Remove mink package causing composer conflict
Perform the following command to make sure you you are not affected by conflicts caused by this package:
Recommended: Enable php-openssl extension
From 5.3.8 and lower
Update sensio distribution bundle
Updating packages with composer
With this command you'll only update all packages that have received updates:
Tip: Legacy extension autoload
Legacy extensions autoload must be regenerated when new classes are added. To make sure to avoid any issues always run this command after composer update:
php ezpublish/console ezpublish:legacy:script bin/php/ezpgenerateautoloads.php --extension
After Updating
Follow all instructions below that applies to the version you've updated from, i.e. if you are updating from 5.3.0 everything applies.
Updating from 5.3.2 and lower
Update the database
Import to your database the changes provided in:
/<ezp5-root>/ezpublish_legacy/update/database/<mysql|postgresql>/5.3/dbupdate-5.3.2-to-5.3.3.sql
And if you use Cluster (DFS) the following:
/<ezp5-root>/ezpublish_legacy/update/database/mysql/5.3/dbupdate-cluster-5.3.2-to-5.3.3.sql
Updating from 5.3.4 and lower
Update Solr configuration and reindex content
An eZ Find user needs to update their solr schema.xml.
For each solr core (located in ezfind/java/solr), you need to edit <my-core-name>/conf/schema.xml
Around line 566, right after:
Add the following lines:
Now restart Solr, and re-index your content to be able to take advantage of this improvement.