Path

ez.no / documentation / ez publish / upgrading


You are now viewing the documentation of eZ Publish legacy (4.x series and the legacy "stack" in 5.x). For 5.x versions this documentation must be complemented with the latest, more current documentation available at confluence.ez.no. Happy learning!

Upgrading

This chapter contains information related to the upgrade of an eZ Publish solution. If eZ Publish is used correctly, then upgrades should be very easy. This means that if you have not tampered with the kernel files, changed the database, the default settings and/or templates, everything should be okay. If you have, then you should know what you are doing.

The following list contains links to the different upgrade procedures. If you haven't done so already, make sure that you have a backup and that your data is in a consistent state (refer to the text below):

Svitlana Shatokhina (08/09/2006 3:02 pm)

Bertrand Dunogier (05/11/2013 4:09 pm)

André R., Andrea Melo, Ricardo Correia, Bertrand Dunogier


Comments

  • permissions

    For Linux users copying their own directories into the eZ Publish directories, it may be helpful to remember to either:
    - use "cp -p" to preserve permissions and ownership, or
    - run bin/modfix.sh after copying them
    to be sure permissions and ownership are set correctly.
  • Upgrading steps

    These are the steps I have used to upgrade 4 complex eZ sites from 3.4 straight to 3.7.3.

    I created a new installation of eZ and put a copy of the old database under it. During the installation script I answered "Leave the database and do nothing".

    Create database
    Copy database from live site
    Install eZ
    Use eZ upgrade tool and phpMyAdmin to synchronize the old data to the new database structure
    Manually set the "container" flag on the custom classes and folders for the system (there is probably a script for this)
    Copy the templates from the live site, change ownership and permissions
    Update override.ini
    Copy any images
    Update template priorities
    Copy the stylesheets
    Clear all the caches
    Integrate new CMS into existing site

    The only odd thing was that the variable name $name didn't work well with 3.7.3 and I used $nname instead.