Path

ez.no / documentation / extensions / ez publish extensions / ez find / upgrading ez find / upgrading to ez find 2.6


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 2.6

Back-up

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

Download eZ Find 2.6 from http://share.ez.no/download-develop/downloads

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 "settings/site.ini.append.php" like this:

[ExtensionSettings]
 
ActiveExtensions[]=ezfind
[...]

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.

Autoload update

Next the autoload array needs to be updated for the extension. To do this, execute following command from eZ Publish root folder:

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

Clear cache

Clear the template override cache with the following command:

php bin/php/ezcache.php --clear-id=template-override

Re-index

Next re-index the content of the site by running the command:

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 2.6 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.

Geir Arne Waaler (09/11/2011 2:00 pm)

Geir Arne Waaler (09/11/2011 2:02 pm)


Comments

There are no comments.