ibexa

Path

ez publish / upgrading / upgrading to 3.4 / from 3.4.x to 3.4.y


Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.

from 3.4.x to 3.4.y

This section describes how to upgrade your existing eZ publish 3.4.x installation to version 3.4.y, for example from 3.4.0 to 3.4.8. If you are upgrading from a version prior to eZ publish 3.4.0, you should first upgrade to 3.4.0 as described here.

Please make sure that you have a working backup of the site before you do the actual upgrade. The upgrade procedure consists of the following steps:

  1. Upgrading the distribution files to 3.4.8
  2. Upgrading the database to 3.4.8
  3. Running the system upgrade scripts
  4. Configuring the smart viewcache cleaning system (optional)
  5. Clearing the caches

Step 1: Upgrading the distribution files

The easiest way to upgrade the distribution files is to unpack eZ publish 3.4.8 to a directory and then copy the directories that contain site-specific files from the existing installation. Make sure that you copy the following directories:

  • design/example
  • design/example_admin
  • var
  • settings/siteaccess
  • settings/override

Replace "example" and "example_admin" with actual names used by your siteaccesses.

Custom extensions

If you are using custom extensions then the subdirectories inside the "extension" directory will also have to be copied. However, make sure that you do not overwrite any extensions that come with eZ publish (for example the "PayPal" extension).

Step 2: Upgrading the database

To upgrade 3.4.0 database to 3.4.8, you should navigate into the eZ publish 3.4.8 directory and run the following database upgrade scripts one after another:

  1. dbupdate-3.4.0-to-3.4.1.sql
  2. dbupdate-3.4.1-to-3.4.2.sql
  3. dbupdate-3.4.2-to-3.4.3.sql
  4. dbupdate-3.4.3-to-3.4.4.sql
  5. dbupdate-3.4.4-to-3.4.5.sql
  6. dbupdate-3.4.5-to-3.4.6.sql
  7. dbupdate-3.4.6-to-3.4.7.sql
  8. dbupdate-3.4.7-to-3.4.8.sql

MySQL

The database upgrade scripts are located in the "update/database/mysql/3.4/" directory of your eZ publish installation. Each of these scripts can be launched using the following shell command:

mysql -u<username> -p<password> <database> < update/database/mysql/3.4/dbupdate-3.4.x-to-3.4.y.sql

PostgreSQL

The database upgrade scripts are located in the "update/database/postgresql/3.4/" directory of your eZ publish installation. Each of these scripts can be launched using the following shell command:

psql -d <database> -U <dbowner> < update/database/postgresql/3.4/dbupdate-3.4.x-to-3.4.y.sql

Step 3: Running the system upgrade scripts

There are no upgrade scripts for upgrading from 3.4.x to 3.4.y.

Step 4: Configuring the smart viewcache cleaning system (optional)

In eZ publish 3.4.2, the caching functionality has been improved (see the 3.4.2 changelog for more information). If you are upgrading to version 3.4.2 or later, then it is recommended to configure the smart viewcache cleaning system. This feature allows to determine which additional nodes the system should clear the caches for when the content of an object is changed (by default, the view cache will be cleared for all published nodes of this object, their parent nodes and nodes of reverse related objects). Please note that this step is only required if you are running a complex site or if you have cache problems after upgrading (for example, if your changes to content are not visible on some pages).

Step 5: Clearing the caches

Whenever an eZ publish solution is upgraded, all caches must be cleared in a proper way. This should be done from within a system shell:

  1. Navigate into the eZ publish 3.4.8 directory.
  2. Run the clear cache script:
    bin/shell/clearcache.sh --clear-all
    

Please make sure that all caches are cleared. Sometimes the script is unable to clear caches because of restrictive file/directory permission settings. Make sure that all caches have been cleared by inspecting the contents of the various cache subdirectories within the "var" directory.

Svitlana Shatokhina (14/09/2006 10:23 am)

Svitlana Shatokhina (11/10/2006 12:46 pm)


Comments

There are no comments.