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):
- Upgrading from 5.1 to 5.2
Svitlana Shatokhina (08/09/2006 1:02 pm)
Bertrand Dunogier (05/11/2013 3:09 pm)
Comments
Upgrading steps
Monday 20 March 2006 1:23:07 am
Betsy Gamrat
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.
permissions
Friday 01 June 2007 3:37:49 pm
Greg McAvoy-Jensen
- 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.