Upgrading Prosper202

Before You Upgrade

Upgrading your Prosper202 software is easy, but back up your database and your 202-config.php file first, every time. An upgrade changes the database in place and there is no downgrade: restoring the database backup taken before the upgrade is the only way back. Putting the old files back is not a rollback: from 1.9.76, the previous version’s code can no longer record conversions against an upgraded database.

Take a full mysqldump of the Prosper202 database (or your host’s database snapshot) after the site stops taking traffic and before you start. The upgrade page and the 1-Click Upgrade page (from the new-version notice under the header) both say so above their button.

READ: Version 1.8.x and higher uses a different 202-config.php file. Follow the instructions below exactly.

Upgrading to 1.9.76

The upgrade takes a 1.9.55 (or older) database to 1.9.76 in one pass. The full list of changes is in changelogs.txt.

• Database version. 1.9.76 needs MySQL 8.0 or newer, or MariaDB 10.6 or newer, and PHP 8.3 or newer. Check your database version before you upgrade by running SELECT VERSION();. Don’t rely on the upgrade page to stop you: in 1.9.76 its check can miss MariaDB 10.1 to 10.5 (that will be fixed in the next release, 1.9.77). A 1-Click Upgrade from 1.9.55 replaces the files before the database step, so check the version first.
• Large installs. The upgrade page answers only when the upgrade has finished; at a million conversions that is one to two minutes, which can outlast your proxy’s or host’s time limit and show a timeout error. The upgrade keeps running on the server regardless: wait a few minutes and reload the page. If it is still running the page says “An upgrade is already running” and changes nothing; once it has finished it sends you to sign in. There is nothing to redo.
• Cron. The attribution worker runs from the minutely cron (202-cronjobs/index.php), or on its own as 202-cronjobs/attribution-worker.php. After the upgrade it brings your existing conversions into multi-touch attribution and builds the report rollup (about 20 minutes of worker time per million conversions); reports compute in full meanwhile and say how far it has got. Check that the minutely cron runs (p202 attribution queue should not keep growing), as described in the multi-touch attribution guide. A cron job run against a database that still needs the upgrade now exits with “the database needs an upgrade” instead of succeeding silently.
• Permissions. The upgrade adds view_attribution_reports and manage_attribution_models; review role assignments under User Management in the account menu. The Mobile Apps pages use the same two permissions.
• Mobile202. The separate 202-Mobile pages are retired; their addresses redirect to the responsive pages.
• Custom deployments. If you install from source rather than the release zip, run composer install --no-dev after replacing the files.

Upgrade Instructions

1. Download the latest version from your account at my.tracking202.com.
2. Back up the database: a full mysqldump or your host’s snapshot, taken after the site stops taking traffic. This is the only way back if anything goes wrong.
3. Back up the 202-config.php file.
4. Delete all the previous files on the domain (this is extremely important, as the old files may have vulnerabilities).
5. Upload all of the new files (you should be uploading to an EMPTY directory after the previous delete).
6. Copy the database settings from your old 202-config.php into the 202-config-sample.php file.
7. Rename the 202-config-sample.php file to 202-config.php.
8. Navigate to your Prosper202 URL and follow the prompts.

That’s it: Prosper202 is upgraded. Newer versions also have the 1-Click Upgrade in the new-version notice under the header.

How-to Upgrade Video

Video: Upgrading Your Prosper202 Installation To Version 1.8.3 (an older version; the steps above are current).