Changed regexps
[squirrelmail.git] / UPGRADE
CommitLineData
47f9c368 1Upgrading from 0.3 or higher
2============================
3
4If you are upgrading from versions 0.3 or higher of SquirrelMail, you can
5use this guide to make the transition a bit smoother. If you have been
6using a previous version (0.1 or 0.2), it is suggested that you just start
7from scratch and configure your settings as if it was your first install.
f4057b81 8
2b996daf 9NOTE: The new plugin architecture required the use of some functions which
10are not in all versions of PHP4. You will need at least PHP4 beta2. If you
11need to upgrade please go ahead and install the latest release version of
12PHP4.
f4057b81 13
141. Backups
15===========
2b996daf 16
17Make a backup of your current SquirrelMail directory. If you use "cp", be
18sure to use the "-Rp" options. -R means recursive, and -p will save the
19permissions in the directory. In this example, we assume that your httpd
20document directory is /home/httpd/html.
f4057b81 21
22 $ cd /home/httpd/html
23 $ cp -Rp squirrelmail-0.4 squirrelmail-0.4.bak
24
25
262. Unarchives Squirrelmail-0.5.tar.gz
27======================================
2b996daf 28Make sure that you're in your httpd document directory (/home/httpd/html)
29and then unarchive the squirrelmail archive (whatever the filename is):
30
f4057b81 31 $ tar -zxvf squirrelmail-0.5.tar.gz
32
33
343. Copy backups in place
35=========================
36Here is the main part. There are two parts to this step: copy preferences,
2b996daf 37and copy config details. The preference files are backwards compatible, so
38it is fine to copy the old user preferences into the new directory.
39However, the configuration file has changed quite a bit, so you will want to
40be sure to run the configure script (conf.pl) to set up any new config
41details.
f4057b81 42
43First, copy the files in place:
44
45 $ cp squirrelmail-0.4.bak/data/* squirrelmail-0.5/data
46 $ cp squirrelmail-0.4.bak/config/config.php squirrelmail-0.5/config
47
48Note that if at all possible, start the configuration process from scratch.
49It is less prone to missing configuration options than copying your old
50configuration. The ideal solution would be to copy your users' preference
51files, and then run conf.pl to re-configure SquirrelMail (without using the
52old config file). If you do copy the config.php file, you will want to run
53conf.pl and check for new options.
54
55
564. Change permissions
57======================
58The web server must have write permission to the data directory. In this
59example, we assume that user "nobody" and group "nobody" are the web server
60as is often the case with Apache.
61
62 $ cd squirrelmail-0.5
63 $ chown -R nobody.nobody data
64
65
665. DONE!
67=========
2b996daf 68That should be all! The most important part is copying your users'
69preference files back into the new data directory. This will insure that
70your users will have their old preferences.