This documentation relates to CiviCRM version 2.2. It's not maintained anymore.
Current version of documentation.


Upgrade Standalone Sites to 2.2

Aller directement à la fin des métadonnées
Aller au début des métadonnées

This page refers to outdated version of CiviCRM. Check current version of documentation.

Documentation Search

CiviCRM 2.2 Documentation

Support and Participation

Developer Resources

Use this document to UPGRADE CiviCRM Standalone installations to the latest 2.2 release from version 2.1x or an earlier version of 2.2
  • Installing from scratch? Instructions are here.
Version 2.2 Requirements

Before beginning this upgrade, verify that your server meets the requirements for CiviCRM 2.2.

  • CiviCRM 2.1.x : You must be running CiviCRM 2.1.x to use this upgrade.
  • PHP 5.x : Starting with the 1.9 release, CiviCRM will NOT run on PHP4 servers* (more info...).
  • MySQL 5.0.x or higher : CiviCRM is compatible the current generally available MySQL release.

Step-by-step Upgrade Procedures

1. Download the v2.2 CiviCRM Package

  • From
  • Select the currently available civicrm-2.2 tarball. Grab the "drupal" tarball. (Even though we're doing a standalone installation, get the "drupal" tarball. The joomla one may work too, but it hasn't been tested.) For Example: civicrm-2.2.x-drupal.tar.gz

2. Backup your CiviCRM database

Refer to the MySQL reference manual or phpMyAdmin documentation if you need information on backing up your database.

3. Backup and then delete all 2.1 code files

CiviCRM will not run properly if 2.1 files are present after the upgrade. Make sure you have a good backup of your complete 2.1 installation and then delete CiviCRM 2.1 codebase.

These commands will do the trick:

4. Unpack the 2.2 package and verify permissions

  • Unpack the 2.2 files to the place where CiviCRM 2.1 existed.
  • Ensure that your CiviCRM/standalone/files directory is writeable by the webserver. You can use the following command to set proper permissions:
  • Copy your files and settings back from the old version

5. Run the Upgrade script

MySQL 4.0 and 4.1 are Not Supported

Support for MySQL versions 4.0 and 4.1 has been discontinued. This means that you may encounter various issues and/or unexpected behavior if you atempt to run CiviCRM under these versions, and the CiviCRM engineering team will not provide support for debugging or resolving these issues. You are strongly encouraged to upgrade to the current generally available release of MySQL.

* Point your web browser to the following URL (you should already be logged in to Standalone with administrator-level permissions. If not logged in do now and proceed.):

* You should see the Upgrade screen.

  • If you are ready to upgrade, click the 'Upgrade Now' button.
  • You should see the message Upgrade successful when the upgrade completes.
    • If you receive any errors during the process, please note down the exact error message, and check for solutions on the community support forum.
  • Now click the Return to CiviCRM home page link. This will rebuild CiviCRM menus automatically and return you to the CiviCRM home dashboard. You should the message Menu has been rebuilt.

6. Verify and Update Resource URL Settings

If you are running this installation in a different directory from your 2.1 site you may need to update the configured CiviCRM Resource URL (Missing icons and images, as well as problems with javascript functions and stylesheets are all symptoms that this setting needs to be updated.)

  • Go to Administer CiviCRM » Global Settings » Resource URLs
  • Refer to the field help on that screen for instructions.

7. Enable Components

If you plan on using the new CiviCase component, or any components that you weren't using in the prior version (e.g. CiviPledge or CiviGrant for grant management) - you'll need to enable these component(s):

  • Go to Administer CiviCRM » Global Settings » Enable Components

If you have been using Cases in 2.1 and / or want to start using the CiviCase component, you will also need to complete additional configuration steps. Learn more...

8. Important Note

Security warning

It is generally considered bad security practice to put an entire system like CiviCRM under the docroot of a web server. This exposes a lot of files and code to potential hackers that really isn't necessary. If you're just testing CiviCRM Standalone on a machine that isn't accessible from the Internet, it's probably not a big deal. But don't even think about setting up a live production server without following these directions.

  • Aucun