This section describes how to upgrade your existing eZ Publish 5.1 installation to version 5.3. Make sure that you have a working backup of the site before you do the actual upgrade, and make sure that the installation you are performing the upgrade on is offline.
Note on Paths
- /<ezp5-root>/: The root directory where eZ Publish 5 is installed in, examples: "/home/myuser/www/" or "/var/sites/ezpublish/"
- /<ezp5-root>/ezpublish_legacy/: Root directory of "Legacy" (aka "Legacy Stack", refers to the eZ Publish 4.x installation which is bundled with eZ Publish 5) normally inside "ezpublish_legacy/", example: "/home/myuser/www/ezpublish_legacy/"
WORK IN PROGRESS
Check for requirements
PHP 5.3.3 and higher is needed. Further information regarding System Requirements can be found on Requirements Documentation Page.
Step 1: Upgrade the distribution files
The easiest way to upgrade the distribution files is to unpack eZ Publish 5.3 to a separate directory and then copy the directories that contain site-specific files from the existing 5.1 installation into "/<ezp5-root>/". Make sure you copy the following directories:
ezpublish_legacy/design/<your designs>(do NOT include built-in designs: admin, base, standard or admin2)
ezpublish_legacy/extension/*(not including the built-in / standalone ones: ezflow, ezjscore, ezoe, ezodf, ezie, ezmultiupload, ezmbpaex, ez_network, ezprestapiprovider, ezscriptmonitor, ezsi, ezfind)
config.cluster.php, if applicable
NB: Since writable directories and files have been replaced / copied, their permissions might have changed. You may have to reconfigure webserver user permissions on specific folders as explained in the file permissions chapter of the installation process.
If you use APC, or an op-code cache solution, make sure to clear the cache. The easiest way is to restart your web server.
Step 2: upgrade custom extensions
If you are using custom extensions, the sub-directories inside the "extension" directory will also have to be copied from the existing 5.1 installation into "/<ezp5-root>/ezpublish_legacy/extension/". However, make sure that you do not overwrite any extensions that are included in eZ Publish distribution, which currently are (Note: As of eZ Publish 5.3, these extensions have the same version number as eZ Publish):
Note that upgrading the distribution files will overwrite the autoload arrays for extensions. You will need to re-generate the autoload arrays for active extensions later.
Important: If you plan to upgrade your eZ Website Interface, eZ Flow or eZ Demo site package as well, then additional extensions will be updated and the step for re-generate the autoload arrays can be skipped until that is done (links to documentation for upgrading these site packages can be found in the last step of this page).
Step 3: upgrade the database
For upgrading the database, you have to jump from 5.1 to 5.2 and then from 5.2 to 5.3.
Import to your database the changes provided in :
Step 4: Apply 5.2 configuration changes
Since default configuration files have been overwritten during step one, the few additions to those files that were made in 5.3 need to be applied manually to the configuration files. All of those changes are additions, none of them replaces what you already have. For most of them, at least one, if not all hierarchy elements (monolog, handler, framework, router...) will already be there. All you have to do is add the missing bits in the existing configuration blocks.
In ezpublish/config/config_dev.yml, add the configuration for the chromephp log handler:
In ezpublish/config/config.yml, you need to add a few default values for the framework
In routing_dev.yml, add the resource import for the SensioDistributionBundle webconfigurator routes:
In ezpublish/config/security.yml, add the following:
If you have added anything to
parameters.yml, we suggest that you add your custom settings to
parameters.yml.dist, so that the composer post-update script handles those, and generates their values correctly.
It is not possible to just copy your old
EzPublishKernel.php file over from the previous installation, since quite a few changes were made to this file in this release. We suggest that you simply reflect in the new kernel file any changes you made in the previous version.
If you had modified composer.json to add your own requirements, you must re-apply those changes to the new version, and run composer install.
Step 5: Update cluster data (if applicable)
If your installation uses the DFS cluster, you are affected by the split DFS tables feature that was added in 5.2. You can also check the DFS setup documentation document on steps 3 and 4 for additional details and usage examples about the newly introduced configurations.
To use the feature, you need to update your DFS database structure. It won't affect existing data, and doesn't require particular measures. Import the following file into yourcluster database (it should be different from your eZ Publish database):
The split table feature stores cache and storage into two different tables. For now, your ezdfsfile table contains both cache and storage. Starting from now, eZ Publish will use the newly created table, ezdfsfile_cache, to store cache. Since the table is empty, it will react as if there was no cache, and work without any changes.
However, we recommend that you remove entries related to cache from your ezdfsfile table. There are several options.
Option 1: unclusterize, clear data, and reclusterize
This method requires that you shutdown the website completely for a little while. It mainly applies to small/medium websites (up to a couple thousand content objects).
May require a lot of disk space
Since this method will create a local copy of every storage file (not including cache) from your NFS to the local server, this method may require a large amount of disk space. You can get an estimate of the required space by running the following query on your cluster database:
It will give you the total size of storage items, in bytes. Remember to escape _ in your vardir.
Use the following commands from your /<ezp5-root>/ezpublish_legacy/ folder:
Next, truncate the ezdfsfile table from your database:
And finally, re-create cluster data based on local data:
Option 2: perform a background cleanup of the storage table
An upgrade script is provided that will let you cleanup the ezdfsfile table on a live website, even with a large cluster. It will delete a configurable (by default 1000) batch of cache rows from ezdfsfile, and sleep (by default for 100 ms) between batches. Run the following from the legacy root:
The script can be interrupted and restarted anytime without risks for the system. We strongly suggest, if you execute it on a live website, that you monitor your database server's performances, and increase the sleep delay and/or decrease the limit if the SQL server's load is too high.
Step 6: Regenerate the autoload array for extensions
To regenerate the autoload array, execute the following script from the root of your eZ Publish Legacy directory:
Step 7: Link assets
Assets from the various bundles need to be made available for the webserver through the web/ document root.
The following commands will first symlink eZ Publish 5 assets in "Bundles" and the second will symlink assets (design files like images, scripts and css, and files in var folder) from eZ Publish Legacy:
Step 8: Update rewrite rules
There are two ways eZ Publish 5 can be installed, either the full install with both the new Symfony stack and the legacy stack, or legacy only. In latter case you only need to point your '4.7 like' rewrite rules to /<ezp5-root>/ezpublish_legacy/ and that's it. Otherwise, update your virtual host according to the eZ Publish 5.2 rewrite rules on confluence and point your host configuration to /<ezp5-root>/web/.
Step 9: Clear 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:
Navigate into the new eZ Publish directory.Run the script using the following shell command:cd /<ezp5-root>/ezpublish_legacy/php bin/php/ezcache.php --clear-all --purgePurging ensures that the caches are physically removed. When the "--purge" parameter is not specified, the caches will be expired but not removed.
Note: 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.