Upgrading from activeCollab 0.6 or 0.7

How to upgrade from activeCollab (versions 0.6 or 0.7) to ProjectPier, currently version 0.8.
These instructions will help you upgrade from activeCollab 0.6, 0.7 beta, 0.7 or 0.7.1 to ProjectPier 0.8. (the current release).

Please note that you can only change from activeCollab to ProjectPier if you are using activeCollab 0.7.1, if you have a previous version you'll need to upgrade your activeCollab installation to 0.7.1. If you already have the most recent version of activeCollab installed (0.7.1) skip to the last section of this document, "activeCollab 0.7.1 to ProjectPier 0.8"

Warning! Back up your data and files!

Before you start any of the following instructions please be sure to backup all your data. Such backup should include data from database and all files from the disk. If you encounter any problems it should be fairly easy to restore the old installation an try again.

Upgrading activeCollab to the newest version

activeCollab 0.6 to activeCollab 0.7

These instructions to update activeCollab from 0.6 to 0.7.1 were taken from Illija Studen's guide from activeCollab.com, any update can be found there.

1. Create a backup of existing system, including installation files and content from your database. Please, don’t skip this step. If something goes wrong you’ll most probably end up with useless installation and you’ll be unable to go back.
2. Clean up old files – you should delete everything from the file system except contents form /config and /public/files folders. They should remain intact because upgrade script will use data from that folders to upgrade existing database and keep your old files in place. It is important to delete files from old installation because new version will not work if it finds old files – it will break.
3. Upload new files – simply upload new activeCollab files, but make sure that you don’t overwrite old files from /config and /public/files folder.
4. Execute upgrade script – Go to /public/upgrade/ page (for example: http://www.myactivecollab.com/public/upgrade/), select upgrade script (Upgrade 0.6 -> 0.7) and click on Upgrade button.
5. Let the script do the work – it can take some time to transform old database and transfer all the data. If everything goes well you should see a bunch of green messages ending with a message telling you that upgrade process is done successfully. If something goes wrong you’ll receive an error message (red text). In that case you should restore your old installation (from backup) and submit a bug report in the Bug reports forum.
6. You’ll fail to login with your old login data. 0.7 version has a new login system and there is no way for it to read your old password value so you’ll need to reset it using Forgot password form. Just enter your email and hit submit button. You can notify all users by using mass mailer tool (in administration) or reset their password manually.[1]
7. Check the bottom of the page if Forgot password form fails.

activeCollab 0.7 beta to activeCollab 0.7

1. Create a backup of existing system.
2. Drop all files except contents of /config, /public/files and /upload folders.
3. Upload files from 0.7 package but make sure that you don’t overwrite files from three folders listed in previous step.
4. That should be it. Just start using new version.

activeCollab 0.7 to activeCollab 0.7.1

This upgrade will work only from 0.7 to 0.7.1. If you are using older version than 0.7 you'll need to upgrade to 0.7 before you can upgrade to 0.7.1. See instructions above.

1. Create a backup of existing system, including installation files and content from your database. Please, don’t skip this step. If something goes wrong you’ll most probably end up with useless installation and you’ll be unable to go back.
2. Clean up old files – you should delete everything from the file system except contents form /config, /cache, /upload and /public/files folders.
3. Upload new files – simply upload new activeCollab files, but make sure that you don’t overwrite old files from /config, /cache, /upload and /public/files folder.
4. Execute upgrade script – Go to /public/upgrade/ page (for example: http://www.myactivecollab.com/public/upgrade/), select upgrade script (Upgrade 0.7 -> 0.7.1) and click on Upgrade button.
5. Let the script do the work – If something goes wrong you’ll receive an error message (red text). In that case you should restore your old installation (from backup) and submit a bug report in the Bug reports forum.

ProjectPier Upgrade

There is no change on the built-in upgrade checker in ProjectPier for pre-release versions of 0.8. 0.8.0-dev and 0.8.0-RC1 and 0.8.0 (the final release) will all be considered 0.8 as far as the upgrade checking utility is concerned. If you have installed a pre-release version -dev or -RC1, you will not receive upgrade notification within ProjectPier.

All versions of ProjectPier 0.8 are database compatible with each other and with activeCollab 0.7.1, and only with 0.7.1, there is no garanteed compatibility with any other version of activeCollab, please be sure to have your installation upgraded to version 0.7.1.

There is no upgrade script for ProjectPier 0.8. because it has the same DB structure as aC 0.7.1

When upgrading, do NOT run the installation scripts!

activeCollab 0.7.1 to ProjectPier 0.8.

1. Backup your database
2. Backup your installation files (you will need your existing /config/config.php to complete this installation).
3. Unzip the ProjectPier package to a new directory on your hard drive, then upload to your server, overwriting the existing activeCollab or ProjectPier installation files.
4. Add the following lines to /config/config.php that you backed up in step 2 (NOT the one you just unzipped, the one you backed up from your existing installation!!) define('SHOW_MESSAGE_BODY', true);      define('SHOW_COMMENT_BODY', true);      define('SHOW_MILESTONE_BODY', true);      define('TOKEN_COOKIE_NAME', '93c65403ce6b695a583e9e4c8c5b25e687283ee8'); 
   • SHOW_MESSAGE_BODY = Set this to true or false, it determines whether to include message text in new message notification emails.
   • SHOW_COMMENT_BODY = Set this to true or false, it determines whether to include comment text in new notification emails.
   • SHOW_MILESTONE_BODY = Set this to true or false, it determines whether to include milestone text in new milestone notification emails.
   • TOKEN_COOKIE_NAME = set this to any unique string of characters, the exact length is not important. This is required, but only used to differentiate between installations when there are multiple installations on the same server.
   • Change from: define('PRODUCT_VERSION', '0.7.1');
     to: define('PRODUCT_VERSION', '0.8.0');
   • Upload /config/config.php that you just edited to your server, overwriting the existing file.
5. You should be ready to go now!

ProjectPier 0.8-RC1 to ProjectPier 0.8-final

Follow these instructions if you were already using the 0.8 RC1 version of PP (ignore this if you are installing PP for the first time).

1. Backup your database
2. Backup your installation files.
3. Unzip the ProjectPier package to a new directory on your hard drive, then upload the following files or directories to your server.
4. (mandatory) - bug fix: /environment/functions/files.php
5. (optional) if you want to make sure you have the latest documentation on your server, copy the following files:
   • changes.txt
   • readme.txt
   • upgrade.txt
6. (optional) The files for Continental Portuguese were added to this release and were not present in previous ProjectPier releases. To use tehm you need to copy the following files to your instalation:
   • /language/pt_pt.php
   • /language/pt_pt/ (directory)
7. To use a Translated, non-english version of ProjectPier: After you've copied the files please open your /config/config.php file, find the line "define('DEFAULT_LOCALIZATION', 'en_us');" and change it to define('DEFAULT_LOCALIZATION', 'pt_pt');. This step is used to change ProjectPier's localization to any other localization of choise, just replace "en_us" with the correct code for the locale you want to use.
8. You should be ready to go now.

[1] If Forgot password fails

You will need to manually update data into database. Open users table and find your administrator user (by username). Update that row and set:

token: 0a92df346e3a833cae214d65af35e69b3cf4e5ab

salt: 6d093346fa02f

twister: 4982716305

That will set password to '123'. Login and update you password. Make sure that mailing is working (you can use Test mailing configuration tool in administration).

Having Problems?

Get help on The Forums