Path / documentation / extensions / ez publish extensions / ez find / upgrading ez find / upgrading to ez find ls 5.0.0

Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Upgrading to eZ Find LS 5.0.0


Before starting the eZ Find upgrading process make sure that you have a working backup of the existing website state including database, extensions, INI settings, etc. During the upgrade process the existing eZ Find extension will be removed and replaced with a new version.


Download eZ Find LS 5.0.0 from

Note: Enterprise customers can download from the download page in the Service Portal

Make sure the extension is activated under the [ExtensionSettings] block in the "ezpublish_legacy/settings/override/site.ini.append.php" like this:


It is important that eZ Find is activated before eZ Webin and eZ Flow, if you use those extensions, to ensure that your installation uses the correct search templates.

Clear ini and template override cache

Clear the ini and template override caches (mandatory) with the following command from your "ezpublish_legacy" folder:

php bin/php/ezcache.php --clear-all

Autoload update

Next the autoload array needs to be updated for the extension. To do this, execute following command from your "ezpublish_legacy" folder:

$ php bin/php/ezpgenerateautoloads.php -e -p


Next re-index the content of the site by running the command, also from your "ezpublish_legacy" folder:

php extension/ezfind/bin/php/updatesearchindexsolr.php -s <admin  siteaccess> --clean

Note: Internally the schema used by Solr has changed, this means that to upgrade to eZ Find LS 5.0.0 a full index update is required. This also means that some attribute names from the old schema might have a different name/format/properties now so every site specific code using Solr defined field names for eZ Publish attributes directly has to be reviewed.

Ricardo Correia (14/02/2013 9:41 am)

Ricardo Correia (18/02/2013 10:55 am)


There are no comments.