Local Software Upgrades | ProVision Documentation (PV Local Installs)

Local Install Upgrade Methods for ProVision (v4.1.20 and newer)

You must be running at least 4.1.20 to follow any of the upgrade methods listed below. If you are not yet at this version, upgrade to 4.1.20 using the old upgrade process first, and then continue using the new upgrade process or contact support for any questions or to schedule an upgrade to the latest version.

There are now 3 different methods to run upgrades:

Old Method

Note: Refer to “Upgrades for ProVision 4.1.19 and earlier” on this page for detailed instructions.

Download the latest ProVision tar file from the ProVision download site.

Extract in web root.

Run the upgrade scripts located in upgrade/scripts in order of version number via php ﹤upgrade-script.php﹥ -v

Command Line

In upgrade/scripts run 'php upgrade.php -h' to get the help and full usage of upgrade.php. This script will automatically get the latest tar file, create a backup, and run all the necessary upgrades between the current and latest version. The most common usage of upgrade will look like this 'php upgrade.php -v -b ﹤/path/to/store/backup﹥'

GUI

In ProVision, navigate to Admin. If there is a new version available, an Upgrade button will be available. Click on the Upgrade Now button to go to the upgrade page. It will automatically download the latest version available, run all upgrade scripts, and create a log of the upgrade process.

Upgrades for ProVision 4.1.19 and earlier

Expand the area below for detailed instructions on upgrading ProVision versions 4.1.19 and earlier:

Upgrades for 4.1.19 and earlier versions

IMPORTANT NOTE FOR 4.1.15 - The configDir.sh script must be run as root after the 4.1.15 tar file is unpacked and before running upgrade-4.1.15.php.

Create a database backup.

mysqldump -u ﹤user﹥ -p﹤pass﹥ ﹤ProVision database name﹥ ﹥ /tmp/ProVisionDBBackup.﹤date﹥.sql

Create a directory backup. Even if you have offsite backup's with ProVision enabled, perform this step to ensure the most current data is saved.

tar -cvf ProVisionFileBackup.﹤date﹥.tar /path/to/webroot

Move the tar file in ProVision web root.

tar -xof productionBuild-4.1.4.tar
This will place all the new files into your web root directory.

Run database upgrades, located in ./dev.

The simple rule of thumb is to run every database upgrade from the version after yours, to the version you want to get to. Here is the short cut list:
If upgrading from 4.1.0 or higher:
php upgrade-4.1.3.php -v
php upgrade-4.1.4.php -v
php upgrade-4.1.5.php -v
php upgrade-4.1.6.php -v
php upgrade-4.1.7.php -v
php upgrade-4.1.8.php -v
php upgrade-4.1.9.php -v
php upgrade-4.1.10.php -v
php upgrade-4.1.11.php -v
php upgrade-4.1.12.php -v
php upgrade-4.1.13.php -v
php upgrade-4.1.14.php -v
configDir.sh ﹤web user﹥ (after tar 4.1.15 tar file unpacked)
php upgrade-4.1.15.php -v
php upgrade-4.1.16.php -v
php upgrade-4.1.17.php -v
php upgrade-4.1.18.php -v
php upgrade-4.1.19.php -v

Check directory/file permissions for the following and make sure they read/write for the web user:

archive
keys
scans
zones
data/globals.php
images/custom

Note: configDir.sh can be run to correct any permissions issues.

Check the imports directory for read/write permission in the configured php session dir.

http://﹤web root﹥/install/configTest.php. If there are any configuration errors listed, they must be corrected.
Login and use!