This section describes how to upgrade your existing eZ Publish 3.0-1 installation to version 3.0-2. If you are upgrading from 2.9.x, then you should first upgrade to 3.0-1 before you can upgrade to 3.0-2.

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.0-2
2. Upgrading the database to 3.0-2
3. Running the system upgrade scripts
4. Updating the system configuration
5. Clearing the caches

Step 1: Upgrading the distribution files

The easiest way to upgrade the distribution files is to unpack eZ Publish 3.0-2 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

There is no need to upgrade 3.0-1 database to 3.0-2 (the appropriate database upgrade script is empty).

Step 3: Running the system upgrade scripts

There are no upgrade scripts for upgrading from 3.0-1 to 3.0-2.

Step 4: Updating the system configuration

You are not required to do any configuration changes when upgrading from 3.0-1 to 3.0-2.

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.0-2 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.