community.egroupware.org: Community wiki

  
Community wiki
Update the Installation

Update the Installation


Before updating your eGroupWare preserve your data!
The procedure depends on the type of the update package (tar, zip, rpm ...):
  1. Go to your eGroupWare directory, usually 'egroupware' in your 'docroot', and save the file 'header.inc.php'.
  2. Create a data backup of your database
  3. depending on the package type: delete or uninstall (rpm) your old installation. You may keep it as a backup by renaming the installation: e.g. under Linux 'mv egroupware egroupware.old'
  4. Install the new package into the same directory (named in 'header.inc.php')
  5. Recover your old 'header.inc.php' by re-copying the backup.
  6. Go to setup (e.g. http://domain/egroupware/setup) in the upper login window

If you get now a 500: Internal Server Error, have a look at Start installation for the solution.

Updates concerning the eGroupWare APIwill be shown in Step 1 - Simple Application Management. You can only go on after the update is imported. You will be asked to do a data backup (Checkbox automatically checked) and then the update will be executed.

Updates concerning only single applications are imported in Step 5 - Advanced Administration of Applications.
You see a table with all applications in the current and the availible version. The symbol shows that an update for this application is availible. As soon as you check the box in the column 'Upgrade', the new version will be installed.

Important to note in 1.4: you have to install egw-pear additionally:
We can NOT package modified PEAR - PHP Extension and Application Repository packages together with eGroupWare, as they have different incompatible licenses. You have to separately download the egw-pear package, unpack it in your eGroupWare install directory and install it via Step 5 - Manage Applications. You have to update FeLaMiMail after that too!


Migration from version 1.2 to 1.4 with adress book contacts in LDAP:
If you were managing your addressbook contacts in version 1.2 in LDAP and want to update to 1.4, you must take the following steps before updating your system!!!:
  1. Transfer the addresses to the database in version 1.2, i.e. export the addresses as eGW SQL.
  2. Update to version 1.4 (see above).
  3. Transfer the data (addresses) back to LDAP with the (configuration of the Addressbook)?.
Attention: If you save the data only in LDAP, the Organisation view is not availible, therefor you have to choose for 'Contacts Repository' at least 'SQL-->LDAP read only'. Besides, you can use LDAP then only to save the contacts if user contacts are also saved in LDAP!

Detailed instruction on update to 1.4 adressbook, contacts stored in LDAP
This instruction was written by Oscar Manuel Gómez Senovilla on 2007/06/10 as an knowledgebase article and modified by Miles Lott.

This is intended mainly for upgrading to new addressbook concept released with egw 1.4, which can cause problems if you use LDAP as backend to store your contacts. There is some documentation and files you may need in addressbook/doc/ and the phpgwapi/doc/ldap/ directory about this, that you should read first before going on, and take this article just to complete some details about upgrading.


Just to prevent problems, don't upgrade directly from any version not being 1.2.x. If you have such old installation, upgrade first to 1.2 and check that everything is working. After this, then you can think about upgrading to 1.4 (taking the next sections into account).
If you use LDAP to store contacts, first make sure contacts are working in 1.2 (with the phpgwcontact schema). Then:

  1. First of all, perform a backup of egw (using the backup option in /setup) for if things go wrong.
  2. Go to addressbook and click "Export contacts". Make sure you select all contacts. Surely you have to select one category at a time, and repeat this for every category (with different filenames, of course). For me, choosing Mozilla LDIF works fine.
  3. Switch your installation to use SQL for contacts. This is a temporary (but necessary) change. You can do this by going to Admin -> Addressbook -> Site configuration, or directly choose "Site configuration" from the menu. Then, choose "SQL" in the dropdown list and save the change (don't change any LDAP setting).
  4. If any, delete all contacts (to prevent duplicates, and remember that you have a backup). If you find too many, you can delete all records from the egw_addressbook table using any db tool.
  5. Import your previuosly exported contacts. It should work straight forward.
  6. For addressbook, you can now upgrade to 1.4, but check anything else about any other egw app or whatever you have elsewhere, including the README at addressbook/doc/.
  7. After upgrading, check that your accounts (which should be in LDAP) are at least listed in Admin-> User accounts.
  8. Go to addressbook and check that your contacts and related data look ok. Remember that you're using SQL for contacts.
  9. Go to Site configuration (in the menu) or Admin -> Addressbook -> Site configuration.
  10. Make sure the LDAP settings are ok. Then, you can remove the contacts from the specified LDAP tree.
  11. Perform the migration from SQL to LDAP. At the bottom, choose the migration type for your installation (usually you should have all in LDAP) and click Start.
  12. Once done, choose LDAP as repository for contacts. After saving your changes, it should work ok.

Update and installation instructions concerning Older-egw-Versions




User Manual / Installation of eGroupWare

The user manual is written by Outdoor Unlimited Training GmbH, who also offers support together with Stylite AG, see eGroupWare support.
You are here