This manual is deprecated. Please visit https://groupoffice.readthedocs.io for the latest documentation. |
Upgrading
Backup your data first! Follow the instructions here: Moving or backup an installation
Contents
Using the Debian/Ubuntu packages
If you are using the professional version or billing module make sure you download the new 3.7 license files first from https://shop.group-office.com/Download and put them in /usr/share/groupoffice.
Then change /etc/apt/sources.list:
deb http://repos.groupoffice.eu/ threeseven main
into:
deb http://repos.groupoffice.eu/ fourzero main
Then run a full system update:
apt-get update && apt-get dist-upgrade
Note: If z-push is installed you'll need to upgrade it manually as described at the ActiveSync page.
Note: In 3.7 the billing module was in the pro package. We have a separate billing package now so if you use that you must run "apt-get install groupoffice-billing" too.
Manual upgrade
If you are using the professional version download the license file and tarbal packages from https://shop.group-office.com/Download. If you use the Community version download the packages from http://sourceforge.net/projects/group-office/.
Take the following steps:
- Backup your database
- Move away your old source files.
- Put the new files at the right location.
- If exists copy your old config.php to the new files.
- Launch Group-Office in your browser and it will perform a system upgrade.
- If z-push is installed you'll need to upgrade it manually as described at the ActiveSync page.
From the Community to Professional version
If you are using the professional version or billing module make sure you download the license files first from https://shop.group-office.com/Download and put them in /usr/share/groupoffice. Then run:
apt-get install groupoffice-pro
If you are using the tar packages download the package from the shop and replace the files.
After this you can login to Group-Office and install the professional modules at Start menu -> Modules.
Upgrading from 3.x to 4.x
If you use LDAP auth. You must change the following in your mapping:
change:
new ldap_mapping_type('function','some_function')
into:
new GO_Ldapauth_Mapping_Function('some_function')
Also be aware that the parameter is no array but a GO_Base_Ldap_Record object.
and:
new ldap_mapping_type('constant','1')
into:
new GO_Ldapauth_Mapping_Constant('1')