-
Notifications
You must be signed in to change notification settings - Fork 3
/
README.txt
99 lines (64 loc) · 3.34 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
ABOUT
eZUpgrade is stand-alone application (not an eZ Publish extension) automating
the process of upgrading an eZ Publish installation.
Using eZUpgrade is as easy as checking it out on the server where the upgraded
installation will reside, inputting some configuration settings, and running
ezupgrade from the command line.
DISCLAIMER
eZUpgrade makes a point of doing as little as possible to the original (source)
installation. Still, the application is delivered as-is without any warranties
of any kind.
You are strongly urged to backup your entire source installation (files and
database(s)) before making use of this application.
SUPPORTED VERSIONS
eZUpgrade is built to be flexible when it comes to adding support for new
eZ Publish versions. Depending on the complexity of the change from one eZP
version to another, adding support could be as easy as adding some
configuration settings to settings/ezupgrade.ini. For more complex changes,
one might need to create some custome upgrade functions.
REQUIREMENTS
* eZUpgrade is dependent upon eZCopy (http://projects.ez.no/ezcopy) and its
requirements.
* eZ Components:
eZUpgrade requires the latest stable release of eZ Components.
To install this, you also need PEAR
See http://ez.no/ezcomponents for more information
HOW IT WORKS
The old eZ Publish installation can be located either on the same server as
the upgraded installation, or on a remote server. If the latter is the case,
eZUpgrade will make use of eZCopy to copy the old installation to the new
server before starting the upgrade procedure.
eZUpgrade then performs the following steps:
1. Downloads and unpacks the distro of the version we want to upgrade to.
2. Copies files (var/, settings/ and extension/) from the old to the
new installation, prompting when overrides are needed.
3. Copies the databases used by the old installation and updates the
database connections in the new installation to the db copies.
4. Performs the upgrade steps needed between the version we are upgrading
from and the version we are upgrading to. This includes sql updates,
upgrade scripts and any other upgrade actions that can be performed
automatically. If there are any upgrade actions that need to be performed
manually, you will be informed.
5. Grants the database user access to the new database(s).
USAGE
From the shell prompt, where eZUpgrade is located, run:
php ezupgrade [account_username]
If you haven't set up any accounts, run `php ezupgrade` to initialize the
configuration wizard.
NOTE ABOUT UPGRADING FROM VERSION 4.X TO 5.0.0
eZUpgrade supports upgrading from any 4.x version to 5.0.0.
IMPORTANT NOTE ABOUT UPGRADING FROM VERSION 3.x TO 4.x
Since 3-series of eZ Publish is run on php4 the upgrading process is a little
more tricky than upgrading from 4.x.y. In order to fix this we have added paths
to php4 and php5 in ezcopy.ini. This means that you need to upgrade on a
server/machine that have both this or do it in cycles.
The way we have upgraded is doing it in cycles. Here is one of our example:
FROM TO
3.5.0 3.8.7
3.8.7 3.9.3
3.9.3 3.10.1
3.10.1 4.0.3
Tip! Instead of upgrading on the server, you could upgrade on your computer
(if its unix based). Download a webserver that have both php4 and php5 set the
paths and run the upgrade. After upgradring copy the last folder to the
webserver and add the database.