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 im= portance of following all steps.

F= rom 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 n= eed to make sure our composer plugins up-to-date, so to :

=20

# First install Composer v1.0 that works with old version of ezpub=
lish-legacy-installer
php -r "copy('https://getcomposer.org/download/1.0.3/composer.phar', 'compo=
ser.phar');"

# As authentication is built in to composer now, we can remove the followin=
g plugin
php -d memory_limit=3D-1 composer.phar remove --no-update --no-plugins bite=
xpert/composer-authstore-plugin


# Then install newer version of ezpublish-legacy-installer that works on Co=
mposer 1.1 (will warn about the outdated versions you have from before)
php -d memory_limit=3D-1 composer.phar update --no-dev --prefer-dist --no-s=
cripts ezsystems/ezpublish-legacy-installer

# Then make sure composer is updated to latests
php -d memory_limit=3D-1 composer.phar selfupdate

=20

From 5.3.2 and lowe= r

Remove Zeta Components packages causing composer conflicts<= /h3>

Issues with Zeta Components and Composer have been fixed (new releas= es of Zeta Components have been made to fix this) so you should edit&n= bsp;composer.json and remove any "zetacomponents" package like shown below:



=20
php -d memory_limit=3D-1 composer.phar remove --no-update zetacomp=
onents/archive zetacomponents/authentication zetacomponents/authentication-=
database-tiein zetacomponents/base zetacomponents/cache zetacomponents/conf=
iguration zetacomponents/console-tools zetacomponents/database zetacomponen=
ts/debug zetacomponents/event-log zetacomponents/feed zetacomponents/image-=
conversion zetacomponents/mail zetacomponents/mvc-tools zetacomponents/mvc-=
authentication-tiein zetacomponents/persistent-object zetacomponents/php-ge=
nerator zetacomponents/signal-slot zetacomponents/system-information=
=20


After doing this, verify that content of composer.json does=
 not contain any entries for zetacomponents/ unless you have y=
our own dependencies on them. ezpublish-kernel and ezpub=
lish-legacy now always requires the specific versions of the Zeta Co=
mponents we use internally.
Update y=
our Nginx configuration
If you're using Nginx as your webserver instead of Apache, then make sur=
e to update Nginx vhost configuration, changes since 5.3.0: 5.3.1,&=
nbsp;5.3.3 
From 5.3.3 and lowe=
r
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=20
 Closed   comp=
oser.json should be edited to take full advantage of the improvement, see t=
he following commit for patch.
From 5.3.4 and lowe=
r
Remove mink package causing composer conflict
Perform the following command to make sure you you are not affected by c=
onflicts caused by this package:

=20
php -d memory_limit=3D-1 composer.phar remove --no-update --dev be=
hat/mink-selenium-driver =20


Recommended: Enable php-openssl extension

This release fixes a vulnerability in the eZ Publish password recovery func=
tion. You need to have the PHP OpenSSL extension (ext-openssl) installed to=
 take full advantage of the improved security, but even without it security=
 is improved. See 
Security Ad=
visory for further information.

From 5.3.8 and lower
Update=
 sensio distribution bundle

=20
php -d memory_limit=3D-1 composer.phar require --no-plugins --no-up=
date "sensio/distribution-bundle ~2.3|~3.0"=20


Updating=
 packages with composer
With this command you'll only update all packages that have received upd=
ates:

=20
# First delete the Symfony container cache to avoid error, on Wind=
ows use something like: DEL /F /Q /S ezpublish/cache/*/*ProjectContainer.ph=
p
rm ezpublish/cache/*/*ProjectContainer.php

# Now update all packages (will warn about outdated bitexpert/composer-auth=
store-plugin package first time you do this before that plugn is removed)
php -d memory_limit=3D-1 composer.phar update --no-dev --prefer-dist=
=20


Tip: Legacy extension autoload


Legacy extensions autoload must be regenerated when new classes are adde=
d. To make sure to avoid any issues always run this command after composer =
update:
php ezpublish/console ezpublish:legacy:script bin/php/ezpgeneratea=
utoloads.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 fr=
om 5.3.2 and lower
Update the database=

Import to your database the changes provided in:
/<ezp5-root>/ezpublish_l=
egacy/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 fr=
om 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 <m=
y-core-name>/conf/schema.xml
Around line 566, right after:

=20
<field name=3D"meta_priority_si" type=3D"sint" indexed=3D"true" =
stored=3D"true" multiValued=3D"true"/>=20


Add the following lines:

=20
<!-- denormalised fields for hidden and visible path elements --=
>
<field name=3D"meta_visible_path_si" type=3D"sint" indexed=3D"true" stor=
ed=3D"true" multiValued=3D"true"/>     <!-- Visible Location path IDs=
 -->
<field name=3D"meta_visible_path_string_ms" type=3D"mstring" indexed=3D"=
true" stored=3D"true" multiValued=3D"true"/> <!-- Visible Location pa=
th string -->
<field name=3D"meta_hidden_path_si" type=3D"sint" indexed=3D"true" store=
d=3D"true" multiValued=3D"true"/>     <!-- Hidden Location path IDs -=
->
<field name=3D"meta_hidden_path_string_ms" type=3D"mstring" indexed=3D"t=
rue" stored=3D"true" multiValued=3D"true"/> <!-- Hidden Location path=
 string -->=20


Now restart Solr, and re-index your content to be able to take advan=
tage of this improvement.

5.3.x Update Instructions

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 im= portance of following all steps.

F= rom 5.3.8 and lower

= Update Composer plugins for Composer v1.1

From 5.3.2 and lowe= r

Update y= our Nginx configuration

From 5.3.3 and lowe= r

Optional: Change = composer.json to avoid occasional fatal error on asset dump when performing= composer update

From 5.3.4 and lowe= r

Remove mink package causing composer conflict

Recommended: Enable php-openssl extension

From 5.3.8 and lower

Update= sensio distribution bundle

Updating= packages with composer

After Updating

Updating fr= om 5.3.2 and lower

Update the database=

Updating fr= om 5.3.4 and lower

Update Solr configuration and reindex content

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 im= portance of following all steps.