Upgrading Vivaldi for MySQL

Upgrading 'In Place'

Upgrading to the newest version of Vivaldi requires the following steps:
  1. Review the Release Notes for the latest updates.  Note whether any release between your current version and the newest version has a small database icon next to it.  That means you will need to run the upgrade.php file.
  2. Download the latest Vivaldi_upgrade.zip file from the customer support site.
  3. If desired, make a backup of your existing Vivaldi deployment directory.
  4. Unzip the downloaded upgrade files, and copy the entire structure to your existing Vivaldi directory, overwriting all existing files if prompted.  Note: Your customerhtmlhead.php, customer.js, customer.css, and database.php files will not be touched or overwitten.
  5. If your version requires a database update, open the file /ogs/upgrade.php on your server to update the Vivaldi database to the latest version.  Note: Your custom forms, menus, security settings, etc. are not touched by the update.  Only Vivaldi system forms, tables, and views.

Parallel Testing

If you want to deploy the upgrade separately from your current deployment and test before applying the changes to production, follow these steps:
  1. Review the Release Notes for the latest updates.  Note whether any release between your current version and the newest version has a small database icon next to it.  That means you will need to run the upgrade.php file.
  2. Download the latest Vivaldi_upgrade.zip file from the customer support site.
  3. Copy your existing Vivaldi deployment directory to the parallel testing location of your choice.
  4. Unzip the downloaded upgrade files, and copy the entire structure to your parallel Vivaldi directory, overwriting all existing files if prompted.  Note: Your customerhtmlhead.php, customer.js, customer.css, and database.php files will not be touched or overwitten.
  5. If your version requires a database update, open the file /ogs/upgrade.php on your server to update the Vivaldi database to the latest version.  Note: Your custom forms, menus, security settings, etc. are not touched by the update.  Only Vivaldi system forms, tables, and views.
Important: This process will update your production database. If you want to perform a fully parallel test before upgrading, copy your production database to a new database, and edit the config/database.php file to point to your test database instance before you run ogs/upgrade.php