Guides
v1.9.78
Guides

Upgrading Prosper202

Back up, check your PHP and database versions, then upgrade Prosper202 to 1.9.78 by hand with the release zip and upgrade.php.

Suggest Edits

Upgrading Prosper202 ClickServer takes a few minutes, but it only goes one way. Read this before you replace any files.

Back up first, every time

  • Dump the database with mysqldump, or take your host's snapshot, once the site has stopped receiving traffic. Save a copy of 202-config.php too.
  • You can't downgrade. The upgrade rewrites the database in place, and from 1.9.76 the old code can't record conversions against it. Restoring the database backup is the only way back; old files alone won't roll it back.
  • Restored a backup? Flush or restart memcached before traffic comes back, because cached row ids can point at rows the backup doesn't have.

What 1.9.78 needs

1.9.78 carries security fixes, so upgrade every install as soon as you can. One pass takes you there from 1.9.77, 1.9.76, or 1.9.55 and older.

Don't wait for a prompt: neither the in-app update notice nor 1-Click Upgrade offers 1.9.78. Use the 1.9.78 zip and the manual steps below.

  • PHP 8.3+, and MySQL 8.0+ or MariaDB 10.6+. Run SELECT VERSION(); yourself first. The upgrade page turns older servers away, but only after you've already swapped the files.
  • Docker or Coolify: rebuild after updating so the container picks up PHP 8.3.36, the October 21, 2026 PHP security release. Redeploy on Coolify; with Compose, docker compose build --pull and then docker compose up -d. Confirm with php -v inside the web container.
  • Afterwards: look through My Account > User Management and delete any user you don't know. An upgrade leaves existing accounts in place.
  • Big installs: the page may time out while the upgrade carries on. Wait a few minutes, then reload.
  • Cron: keep the minutely cron (202-cronjobs/index.php) running. Coming from 1.9.55 or older, it moves existing conversions into multi-touch attribution. A failed run now shows up: exit code 1 (HTTP 500 if your monitor calls it over the web), with the reason in 202-config/cronjob.log.
  • Automatic click deletion (from 1.9.76 or older): if My Account > Settings has "Delete click data older than" switched on, the first cron run after the upgrade starts removing those clicks. Set it to 0, or raise it, beforehand if you want them kept.
  • Chat history (from 1.9.76 or older): the old in-app chat's two local tables are deleted, since chat now lives with the chat service. Only your backup brings them back.
  • Roles: coming from 1.9.55 or older, review My Account > User Management for the new view_attribution_reports and manage_attribution_models permissions.
  • AI assistants: with Prosper202 ClickServer Pro, claude.ai can connect through https://mcp.tracking202.com/mcp once you approve it on your install, and desktop apps can use p202 mcp. See Prosper202 ClickServer API.
  • From source: run composer install --no-dev after replacing the files (it needs PHP's mbstring extension). Compiling the p202 CLI yourself takes Go 1.25 or newer.

Manual upgrade

  1. Get the latest release from your account: download Prosper202 ClickServer.
  2. Back up the database and 202-config.php.
  3. Remove every old file from the domain, since old files can carry vulnerabilities, then upload the new release into the empty directory.
  4. Copy your database details from the old 202-config.php into 202-config-sample.php, then rename it 202-config.php. Versions 1.8.x and later use a different config file.
  5. Open your Prosper202 URL; it forwards you to 202-config/upgrade.php. Follow the prompts there.

📘

Full guide on prosper.tracking202.com

Every 1.9.78 upgrade note in detail, the attribution worker and cron checks, and the changelog: how to upgrade Prosper202 ClickServer to 1.9.78

Updated about 7 hours ago

Did this page help you?