Upgrade to a New Revision - Drupal - CiviCRM Documentation

CiviCRM is a quickly evolving project. We often distribute revisions of the same version to fix bugs, improve performance, or meet specific needs in the community. These are the steps for upgrading an existing site to a newer revision of the same version.

Versions and Revisions
CiviCRM uses a three part numbering system for versions and revisions:

Versions are indicated by the first two numbers.
2.1.x indicates some revision of version 2.1

Revisions are indicated by the number after the second decimal point.
2.1.0 is the first revision of version 2.1

This Procedure is NOT for Version Upgrades

Upgrading to a new VERSION of CiviCRM (i.e. from v1.9 to v2.0.0) generally will involve database and configuration file upgrades in addition to downloading new code. Do not use this procedure for version upgrades - specific procedures will be documented with each new version release.

This Procedure is for DRUPAL sites only

For Joomla sites, please check Upgrade Joomla Sites to 2.0

1. Backup the CiviCRM codebase

Back up the civicrm codebase. Generally this is located in ...sites/all/modules/civicrm/ within your Drupal root directory).

// Change directories to the modules directory.
cd .../sites/all/modules/
// Move the files to back up directory somewhere OTHER than under the modules directory
// This example moves it to a civicrmbackup directory under your home directory
mv civicrm/ ~/civicrmbackup/

Make sure that you move the civicrm backup directory out from under the modules directory. Having two CiviCRM directories below ../modules will definitely cause problems.

2. Download latest revision of CiviCRM

You can find the latest stable revision at http://sourceforge.net/project/showfiles.php?group_id=177914

// Wget the file (modify this line to use the current tarball file name for the version you want)
// Run this command from ..../sites/all/modules
Wget http://downloads.sourceforge.net/civicrm/civicrm-2.0.2-drupal.tar.gz

3. Take the site Offline (for production site upgrades)

When upgrading a production site, it is recommended that you take your site offline during the upgrade process.
Administer » Site Configuration » Site Maintenance

4. Unpack the revision

Untar (i.e. unpack) the new codebase (from ...sites/all/modules in your Drupal root directory).

// Un-tar the file (modify this line with your actual downloaded filename)
tar -xzf civicrm_download_file.tgz

5. Reset Your User Session and Cleanup Template Cache

Temporarily enable CiviCRM debug features:
- Go to Administer CiviCRM » Global Settings » Debugging
- Set Enable Debugging to Yes and click Save.
Click the Administer CiviCRM menu (or any other CiviCRM menu item). After the page is loaded, add two additional query string values (sessionReset=2&directoryCleanup=1) to the URL in your browser's location bar, and reload the page. (You may see a large number of missing file warning messages on your screen - depending on how your Drupal Error Reporting option is configured. These are expected and will disappear on the next page request.)
```
// Example URL
http://...../?q=civicrm/admin&sessionReset=2&directoryCleanup=1

// Example with Clean URLs
http://...../civicrm/admin?sessionReset=2&directoryCleanup=1
```
Now reset Enable Debugging to No and click Save.
Do Not Leave Debug Features Enabled for a Public Site
Debugging should be disabled for publicly available sites as it may allow browsers to view system configuration information.

6. Put the site online (for production site upgrades)

Toggle the following feature, and put your site back online:
**Administer » Site maintenance* (In Drupal 5, this is in "Admin » Site Configuration » Site Maintenance")*
Review your upgraded site and verify that your data is intact.

7. Verify your installation

If you have a problem, check the installation trouble-shooting page, and search the CiviCRM Forums.