ez-publish-community-project-2012-04

Upgrade Notes

Upgrading from eZ Publish Community Project 2012.3 to 2012.4

This section describes how to upgrade your existing eZ Publish Community Project 2012.3 installation to build 2012.4. 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.

Important upgrade notes:

The procedure for upgrading from eZ Publish Community Project build 2012.3 to build 2012.4 consists of the following steps:

• Backing up the website
• Putting the website offline (optional)
• Upgrading the database
• Upgrading the distribution files to 2012.4
• Upgrading custom extensions
• Regenerate the autoload array for extensions
• Clearing the caches
• Putting the website online (optional)

Check for requirements

It is recommended to always verify the requirements for the new version of eZ Publish before attempting an upgrade. eZ Publish Community Project 2012.3 is compatible with PHP version 5.3 and above. So is eZ Publish Community Project 2012.4. For more information regarding system requirements check out http://doc.ez.no/eZ-Publish/Technical-manual/4.6/Installation/Requirements-4.6

Step 1: Backing up the website

• Filesystem set: the extension and settings folders, plus any other folder where you have put your custom developments in (e.g. design/mydesign)
• Content set: the var/storage, var/<vardir>/storage folders, and a dump of the database (nb: for ezdb cluster mode, a dump of the storage database is needed instead of the storage folders; for ezdfs cluster mode both a dump of the storage database and a backup of the shared var folder on nfs)
• Optional: the complete installation directory of eZ Publish, except for the var directory and for the eZFind index directory. This is mandatory if you have customized the .htaccess or config.php files

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

Step 2: Putting the website offline (optional)

This step is recommended but not mandatory

• Put the public website offline and set up a courtesy page to prevent end users from accessing the website while you upgrade. This involves generally modifying the webserver configuration. Make sure you have a different vhost available to access the public website using a private IP address or hostname during the upgrade process
• Disable execution of eZ Publish cronjobs

Step 3: Upgrading the database

MySQL

Run the following against your MySQL database :

 <span>SET</span> storage_engine<span>=</span>InnoDB; <span>UPDATE</span> ezsite_data <span>SET</span> value<span>=</span><span>'4.7.0rc1'</span> <span>WHERE</span> name<span>=</span><span>'ezpublish-version'</span>; <span>UPDATE</span> ezsite_data <span>SET</span> value<span>=</span><span>'1'</span> <span>WHERE</span> name<span>=</span><span>'ezpublish-release'</span>;   <span>UPDATE</span> eztrigger <span>SET</span> name <span>=</span> <span>'pre_updatemainassignment'</span>, function_name <span>=</span> <span>'updatemainassignment'</span>   <span>WHERE</span> name <span>=</span> <span>'pre_UpdateMainAssignment'</span> <span>AND</span> function_name <span>=</span> <span>'UpdateMainAssignment'</span>; <span>ALTER</span> <span>TABLE</span> <span>`ezdfsfile`</span> <span>CHANGE</span> <span>`datatype`</span> <span>`datatype`</span> VARCHAR<span>(</span><span>255</span><span>)</span>; <span>ALTER</span> <span>TABLE</span> <span>`ezdbfile`</span> <span>CHANGE</span> <span>`datatype`</span> <span>`datatype`</span> VARCHAR<span>(</span><span>255</span><span>)</span>;

Postgresql

Run the following against your Postgresql database :

 <span>UPDATE</span> ezsite_data <span>SET</span> value<span>=</span><span>'4.7.0rc1'</span> <span>WHERE</span> name<span>=</span><span>'ezpublish-version'</span>; <span>UPDATE</span> ezsite_data <span>SET</span> value<span>=</span><span>'1'</span> <span>WHERE</span> name<span>=</span><span>'ezpublish-release'</span>;   <span>ALTER</span> <span>TABLE</span> ONLY ezpending_actions     <span>ADD</span> CONSTRAINT ezpending_actions_pkey <span>PRIMARY</span> <span>KEY</span> <span>(</span>id<span>)</span>;   <span>UPDATE</span> eztrigger <span>SET</span> name <span>=</span> <span>'pre_updatemainassignment'</span>, function_name <span>=</span> <span>'updatemainassignment'</span>   <span>WHERE</span> name <span>=</span> <span>'pre_UpdateMainAssignment'</span> <span>AND</span> function_name <span>=</span> <span>'UpdateMainAssignment'</span>;

Step 4: Upgrading the distribution files

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

• design/<mydesign>
• design/<mydesign_admin>
• var
• settings/siteaccess
• settings/override

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):

• 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 

• Alternative shell commands

 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 varchown -R <webuser>:<webusergroup> design extension settings var 

Step 5: Custom extensions

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 2012.4 tarball, which are currently:

Bundled and enabled

• ezautosave-1.0.0-rc1
• ezgmaplocation-1.5.0-rc1
• ezie-1.4.0-rc1
• ezjscore-1.5.0-rc1
• ezmultiupload-1.6.0-rc1
• ezodf-2.8.0-rc1
• ezoe-5.5.0-rc1
• ezprestapiprovider-1.2.0-rc1
• ezstarrating-1.5.0-rc1
• eztags-1.3.0-dev

Bundled but not enabled

• ezcomments-1.4.0-rc1
• ezfind-2.7.0-rc1
• ezformtoken-1.1.0-rc1
• ezscriptmonitor-1.4.0-rc1

Optional installation (depending on the package chosen during the installation wizard)

• ezflow-2.5.0-rc1
• ezwebin-1.10.0-rc1
• ezwt-1.6.0-rc1

Step 6: Regenerate the autoload array for extensions

To regenerate the autoload array, execute the following script from the root of your eZ Publish installation:

php bin/php/ezpgenerateautoloads.php --extension

Step 7: Clearing the caches

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.

Step 8: Putting the website back online

This step is optional, and is only needed if you put the website offline at step 2

• warm up the template cache by pre-compiling template files. This should be done from the root directory of your eZ Publish installation:

php bin/php/eztc.php --wwwdir=<value> --index-file=<value> 

• re-enable the cronjobs
• warm up the content cache: use a tool such as curl or wget that will navigate the website to force eZPublish to generate the view cache for all content
• change the webserver / firewall configuration to allow public access to your website again