Update

Update

CRM can be updated by simply replacing all the files with the latest version. If a version upgrade requires extra work, there will be scripts provided in the scripts/migration directory. Instructions for downloading and uncompressing the files are in the Installation directions.

Backup

Back up the database and uploaded media before you begin the upgrade. Even if it's not a major update, it doesn't hurt to make a backup. You might also back up your configuration.inc. You can move it back into place after the upgrade.

Install new version

The configuration file and the media are the only things that get modified from the default installation. This means, usually, after backing up, you can just delete your existing installation and replace it with the new version. Then you can just put your old media files back in place, and move configuration.inc back into place.

For zero downtime, you can also keep all your existing files in place, and just copy the new version over the top of your existing installation. The only downside to this technique is that during development, scripts become obsolete and are deleted from the application. These obsolete files will not be removed if you copy over your existing installation.

Double check to make sure Apache still has permission to write files into the data directory.

Check for new configuration options

There are a few new configuration settings that must be added to your previous configuration.inc. You can copy the default settings from configuration.inc.default into your previous configuration.inc. Inside configuration.inc.default, look for, and copy these settings into your previous configuration.inc.

Run any upgrade scripts

Some version involve changes to the data or directory structure of the installation. When these changes occur, upgrade scripts are provided in scripts/migration. After any upgrade, you should check in scripts/migration and apply any scripts that appropriate. If you are updating across multiple versions, be sure to apply each version's update scripts in order.

MySQL scripts

Updates to the mysql database are written in SQL and have the .sql extension. The easiest way is the mysql client.

mysql crm < migrations/x.x-x.x/update_stuff.sql

PHP scripts

More complex updates are written in PHP. These need to be run on the server using the PHP command line.

php migrations/x.x-x.x/update_stuff.php

Update your Solr schema.xml

If the new version has made changes to the Solr schema, we will include a copy of the new schema.xml inside the scripts/migration/ directory. If you don't see a new schema.xml there, then no changes have been made, and there's no need to reindex.

If there is a schema.xml inside of scripts/migration/ you'll need to replace your current Solr core's schema.xml with the new version and re-index the Solr search engine.

cd /crm/scripts/solr
php indexSearch.php