These instructions take advantage = of the C= omposer powered update systems in= 5.4 for maintenance updates, so make sure:
For Upgrading from versions pr= ior to 5.3 look at the Installation and Upgrade Guides.
You will also find, at the end of = this document, a list of new, optional packages that were made available during the maintenan= ce phase of this version.
Follow all* instructions below that applies to the version you're= updating from: when updating from 5.4.0 everything applies.
* The version you update to will always be the latests, hence the im= portance of following all steps.
Newer versions of Composer sometimes updates it's API's and as such we n=
eed to make sure our composer plugin ezpublish-legacy-installer i=
s up-to-date before we do anything else, so if you don't already have
# 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');"
# Then install newer version
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
Perform the following command to make sure you you are not affected by c= onflicts caused by this package:
php -d memory_limit=3D-1 composer.phar remove --no-update --dev beh= at/mink-selenium-driver=20
php -d memory_limit=3D-1 composer.phar require --no-update symfony/= symfony:~2.7.0 sensio/distribution-bundle:~3.0=20
The XmlText fix for EZP-23513 (see https://github.com/ezsystems/ezpublish-kernel/pull/1087) deprecates/r= emoves the CustomTags pre-converter in favor of a new Expanding converter. = While they're not part of the public API, if you rely on this file in any w= ay, you might want to check and update your code.
The legacy, v1 REST API, is now integrated to the Symfony Kernel. This a= llows interaction between this channel and new stack caches (persistence an= d HTTP). It mainly affects the Content Staging legacy extension. Remove the= following line from your rewrite rules and restart your web server:
RewriteRule ^/api/[^/]+/v1/ /index_rest.php [L]=20
rewrite "^/api/[^/]+/v1" "/index_rest.php" last;=20
Edit ezpublish/EzPublishKernel.php, and instantiate&nb=
sp;eZ\Bundle\EzPublishLegacySearchEngineBun=
dle\EzPublishLegacySearchEngineBundle =
;in the list of enabled bundles in the $bundles arra=
y in the registerBundles() method, right before=
EzPublishLegacyBundle.
Make sure you are using Symfony 2.7, as Symfony 2.8 is currently not sup= ported (both are LTS releases, but 2.8 introduced a few breaks that cau= ses problems). So check version using command below, and if 2.8 follow instuctions above to correct it:
php -d memory_limit=3D-1 composer.phar show --installed=20
With this command you'll update all packages that have received updates:=
# 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 php -d memory_limit=3D-1 composer.phar update --no-dev --prefer-dist=20
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
Follow all instructions below that applies to the version you= 've updated from, i.e. if you are updating from 5.4.0 everything applies.
An eZ Find user needs to update their solr schema.xml file.=
For each solr core (located in ezfind/java/solr), you need =
to edit <my-core-name>/conf/schema.xml
Around line 566, right after:
<field name=3D"meta_priority_si" type=3D"sint" indexed=3D"true" = stored=3D"true" multiValued=3D"true"/>=20
Add the following lines:
<!-- 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 a= dvantage of this improvement.
New features are sometimes backported from the development version as ex= ternal packages. They can be installed on top of your existing installation= .
You may also install the ezsystems/ezplatform-solr-search-eng=
ine package, compatible with eZ Publish Platform kernel 5.4.5 and hi=
gher. You can read more about that on the 5.4.5 release notes.
Follow install instructions on the dedicated Solr Search Engine Bundle page.