Testimonials
What our customers say about Team Password Manager

How to upgrade Team Password Manager to the latest version

Current Team Password Manager version: 7.78.161

To upgrade your installation of Team Password Manager to the latest version follow the next steps.

IMPORTANT: v. 7.x+ of Team Password Manager requires at least PHP 5.6 (PHP 7.0+ supported but 7.1 not yet). Make sure you have the appropriate version of PHP in your system. In addition, if you need to use two-factor authentication, you'll need the GD2 library to be able to generate QR codes. (You'll still be able to configure two-factor authentication without QR codes, but it's much easier with them.)

Note if you're using LDAP: before doing anything check that you have a user with Admin/IT role that doesn't authenticate using LDAP (and check that you can sign in). If, for any reason, LDAP doesn't work with the new version, you'll be able to upgrade with this Admin/IT user.

As a safety measure, make a complete backup of your current installation of Team Password Manager before executing these steps. Be sure to backup the files and also the database tables. Read How to make a backup of Team Password Manager for more information.

Also check these notes at the end before starting the upgrade.

Steps to upgrade

1. Download the latest version of Team Password Manager from http://teampasswordmanager.com/download/

2. Decompress the downloaded file on your computer. You'll get a bunch of files and folders. The important ones are the css, import, system and wmm folders, and the index.php file.

3. Replace the css, system and wmm folders and the index.php file from your installation of Team Password Manager with the new ones.

Notes:

  • Be careful not to overwrite the config.php and folder.php files and the uploads folder.
  • Language files are located in the wmm/language folder. The Team Password Manager zip file includes only the English (en) files, so copy the ones you need in this folder. You can get all the available language packs in the language packs page. If you've created custom language files, be sure to back them up before replacing the wmm folder.

4. If you don't have a folder called import, copy it from the decompressed files and make it writable by the web server (give it 666 or 777 permissions). If this folder already exists, make sure it is writable by the web server.

5. If you don't have a folder called uploads, copy it from the decompressed files and make it writable by the web server (give it 666 or 777 permissions). If this folder already exists, make sure it is writable.

6. Execute the upgrade procedure by pointing your browser to web_location_of_teampasswordmanager_files/index.php/upgrade (Example: http://teampasswordmanager.mydomain.com/index.php/upgrade) and follow the instructions. If you get a blank screen instead, it's possible that you need to update the Ioncube loader. Please check the logs in this case.


Important notes

  • We advise you to delete the following files from your Team Password Manager folder: install.txt, eula.txt and upgrade.txt.
  • If you're using Apache 2 with FPM/FastCGI:
    1. Set this parameter in config.php: define('TPM_URI_PROTOCOL', 'PATH_INFO');. More information on TPM_URI_PROTOCOL.
    2. Set cgi.fix_pathinfo=1 in php.ini (Restart Apache after doing changes in php.ini).
    3. If you want to use the API, put this directive in the virtualhosts file or .htaccess (in the root of TPM): SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0
  • If you're using Apache 2 with CGI/FastCGI:
    1. Set cgi.fix_pathinfo=1 in php.ini (Restart Apache after doing changes in php.ini).
    2. If you want to use the API, put this directive in the virtualhosts file or .htaccess (in the root of TPM): SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0
  • If you're using IIS:
    1. Set cgi.fix_pathinfo=1 in php.ini.
    2. Allow double escaping.
Questions or Problems? Please contact our support department