Upgrading from 0.6.8 to 0.6.9
Zurück | Anhang B. Manually upgrading moregroupware | Weiter

## Upgrading from 0.6.8 to 0.6.9

| Anmerkung
These instructions are also valid for upgrades from earlier 0.6.9 CVS versions to the released version.

| Warnung
There have been incompatible changes to the projects module. If you use this module, try out this new version in a seperate installment to see if it (still) fits your needs. Upon upgrading the list of projects should be carried over (and the timesheets data should survive, although invisible), but please be careful.

Here is what to do (Unix style, log in to server first):

1. Backup your 0.6.8 directory!!!

   `cd /one/folder/above/moregroupware`

   `cp -R moregroupware moregroupware.bak`

2. Backup your database!!!

   `mysqldump --add-drop-table -a -u [user] -p [dbname] > ~/mgw068.sql`

3. Get the new release from sourceforge.net.

4. Move the webmail2 store folder to it's new location (you can safely delete the cache folders).

   former structure: `mgw/modules/webmail2/store/0`

   new structure: `mgw/data_store/webmail2/0`

5. Move the files module store folder to it's new location.

   former structure: `mgw/modules/files/store/`

   new structure: `mgw/data_store/files/`

6. Make the data_store folder (and the subfolders!) writable for the webserver.

7. Delete everything in the more.groupware root folder except(!) `data_store`, `config.inc.php` and `templates_c`.

8. Unpack the new files from the archive(s).

   `cd /one/folder/above/moregroupware`

   `tar xzf moregroupware_0_6_9.tar.gz`

9. Now edit `config.inc.php`.

   - Remove the line `$appconf['rootpath'] = ...` (if present).

   - Add the forcessl parameter (if not already present):

         $appconf['forcessl'] = 0;

   - Add a trailing slash to rooturl (if missing):

         $appconf['rooturl'] = 'http://.../mgw/';

   - If present, remove the following lines:

         $appconf['html_compressor'] = false;
         $appconf['html_compressor_debug'] = false;

   - Add the following lines (if missing):

         $appconf['mgw_version_number'] = '0.6.9';
         $appconf['mgw_version_name'] = 'Security';

   - Change the following line:

         $appconf['mgw_version'] = '0.6.8 - Nick';

     to

         $appconf['mgw_version'] = '0.6.9 - Security / Update';

10. Open up your browser and log in to more.groupware as admin, the general module is updated automatically.

    Log in as admin again, the update for the overview module is done.

    Go to the module manager and install the Admin2 module.

11. Now go to every installed module as admin to call the update procedure.

12. Check for the correct renaming of webmail2 tables:

    - Access the database, e.g. with phpMyAdmin.

    - The table names must now be `mgw_webmail2_accounts`, `mgw_webmail2_messages` and so forth instead of `mgw_webmail_accounts`, `mgw_webmail_messages`. In other words, `webmail2` must be used instead of `webmail`.

13. Check whether the emails in webmail2 have the new store path in the database:

    - Access the database, e.g. with phpMyAdmin.

    - View the contents of the table `mgw_webmail2_messages`.

    - The `msg_body` field must always begin with `../../data_store/webmail2/` (except for `docu1.eml` where it has to be `docu/`).

14. Now go to the Admin2 module and set the permissions for your users/groups for the modules. Important: the 'Access Module' permission.

15. If all is up and running, you can safely delete the backup files and the SQL dump created in steps 1 and 2.

If you run into trouble, you can revert back to the old release by removing the new moregroupware directory, moving back the backup dir and just piping the backup SQL into the database:

`rm -ri moregroupware`

`mv -i moregroupware.bak moregroupware`

`mysql -u [user] -p -e "DROP DATABASE [dbname]"`

`mysql -u [user] -p -e "CREATE DATABASE [dbname]"`

`mysql -u [user] -p [dbname] < mgw068.sql`

Zurück | Nach oben | Weiter
Upgrading from 0.6.7 to 0.6.8 | Zum Anfang | Upgrading from 0.6.8/0.6.9 to 0.7.0