This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal
This section describes how to upgrade your existing eZ Publish Community Project 2011.8 installation to build 2011.9. Make sure that you have a working backup of the site before you do the actual upgrade, and make sure the installation you are performing the upgrade on is offline.
The procedure for upgrading directly from eZ Publish Community Project build 2011.8 to build 2011.9 consists of the following steps:
It is recommended to always verify the requirements for the new version of eZ Publish before attempting an upgrade. eZ Publish Community Project 2011.8 is compatible with PHP version 5.3 and above. So is eZ Publish Community Project 2011.9. For more information regarding system requirements check out http://doc.ez.no/eZ-Publish/Technical-manual/4.5/Installation/Requirements-4.5
Tip: if you have many user sessions, and the session data is stored in the database, it might be a good idea to remove all data from the session table before backing it up
Tip: in ezdb and ezdfs cluster modes, it is a good idea to clear all caches before dumping the storage database, as it is not easy to only backup storage and not caches
This step is recommended but not mandatory
The easiest way to upgrade the distribution files is to unpack eZ Publish 2011.9 to a separate directory and then copy into it the directories that contain site-specific files from the existing installation. Make sure that you copy the following directories:
Replace "mydesign" and "mydesign_admin" with the actual names of your designs.
Important note: Because the new directory has replaced the original directory, the directory permissions need to be fixed. Use the following commands to do this.
(You have the choice between Shell commands or Alternative shell commands):
These shell commands will give proper permission to the web server:
cd </path/to/your/eZ/Publish/directory> chmod -R a+rwx design extension settings var
These commands will setup the permission more correctly, but require knowledge about the user account used for running the web server process.cd </path/to/your/eZ/Publish/directory>
cd </path/to/your/eZ/Publish/directory> chmod -R og+rwx design extension settings var chown -R <webuser>:<webusergroup> design extension settings var
If you are using custom extensions, the sub-directories inside the "extension" directory will also have to be copied. However, make sure that you do not overwrite any extensions that are included in the eZ Publish 2011.9 tarball, which are currently:
Run the following against your database (valid for MySQL, Postgresql and Oracle):
UPDATE ezworkflow_event SET data_text5 = data_text3, data_text3 = '' WHERE workflow_type_string = 'event_ezmultiplexer';
To regenerate the autoload array, execute the following script from the root of your eZ Publish installation:
php bin/php/ezpgenerateautoloads.php --extension
Run the following commands from the root directory of your eZ Publish installation:
php update/common/scripts/4.6/removetrashedimages.php -s <SITE_ACCESS> php update/common/scripts/4.6/updateordernumber.php -s <SITE_ACCESS>
eZ Find now embeds Solr 3.1 (the version of eZ Find is now 2.5), this requires a full re-indexing of the content if upgrading form an older version of Solr.
Whenever an eZ Publish website is upgraded, all caches must be cleared in a proper way. This should be done from the root directory of your eZ Publish installation:
php bin/php/ezcache.php --clear-all --purge
Tip : Purging ensures that the caches are physically removed. When the "--purge" parameter is not specified, the caches will be expired but not removed.
Sometimes the script is unable to clear all cache files because of restrictive file/directory permission settings. Make sure that all cache files have been cleared by inspecting the contents of the various cache sub-directories within the "var" directory (typically the "var/cache/" and "var/<name_of_siteaccess>/cache/" directories). If there are any cache files left, you need to remove them manually.
This step is optional, and is only needed if you put the website offline at step 2
php bin/php/eztc.php --wwwdir=<value> --index-file=<value>