...
Read more on the Web servers page.
Step 5: Run composer update
Run composer update --no-dev --prefer-dist to get the latest eZ Publish dependencies.
At the end of the process, you will be asked for values for the parameters previously added to parameters.yml.dist.
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:
| Code Block |
|---|
cd ezpublish_legacy php bin/php/ezpgenerateautoloads.php --extension |
Step
...
7: Link assets
Assets from the various bundles need to be made available for the webserver through the web/ document root.
...
| Code Block |
|---|
php ezpublish/console assets:install --symlink php ezpublish/console ezpublish:legacy:assets_install --symlink php ezpublish/console assetic:dump --env=prod |
Step
...
8: 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.
Step
...
9: Upgrade Extensions (site package)
Next, depending on if you originally installed eZ Flow, eZ Webin or eZ Demo site, follow the steps mentioned in the eZ Webin, eZ Flow or eZ Demo upgrade documentation.