Installation Instructions for Version 2.0 This page provides instructions for manually installing CiviCRM 2.0 for Drupal. Unless you are working with a multi-site configuration, we strongly recommend using the Automated Installer Instructions. Before beginning the install process, please verify that your server meets the requirements for CiviCRM 2.0. PHP 5.2 + : Starting with the 1.9 release, CiviCRM will NOT run on PHP4 servers* (more info...). MySQL 5.0.x or higher with INNODB support : CiviCRM is compatible the current generally available MySQL release. Drupal 5.x : CiviCRM is compatible with the current generally available Drupal release. If you are upgrading from v1.9 to v2.0 - use these instructions. If you are upgrading from v1.8 to v1.9 - use these instructions.

1. Server Requirements

CiviCRM for Drupal has been developed and tested by our team on the following 'recommended' platforms:

• Linux
• Apache 2.0
• PHP 5.2.x
• MySQL 5.x with INNODB enabled
• Drupal 5.7

As of version 1.9 - CiviCRM is not compatible with any version of PHP 4.

Caution: Under Linux, the optional CiviMail component requires PHP 5.X with SOAP and DOM extensions, MySQL 4.1.X+, Postfix 2.2 (a mailer), and Perl 5.8.X. (more info...)

Successful installations have also been done with:

• Darwin (Mac OSX)
• lighttpd 1.5 + PHP5 fastcgi
• Apache 1.3
• MAMP (Mac OSX)

Installing on your own server?

• Notes for installing and configuring Apache 2, MySQL and PHP can be found here.

  Zend Optimizer Compatibility CiviCRM is fully compatible with the current release of Optimizer - 2.5.10. However, CiviCRM will not run with Zend Optimizer release 2.5.7. To verify if you have Zend Optimizer running, and which version: With Shell Access $ php -i No Shell Access // Create a new php file with the following line in it: <?php phpinfo(); ?> // Save as phpInfo.php and upload to a browsable directory on your web-server // Point your browser to the file and review the output In either case, look for Zend Optimizer version in the Copyright information near the top of the output: Example PHP Info Display This program makes use of the Zend Scripting Language Engine: Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies with Zend Extension Manager v1.0.6, Copyright (c) 2003-2004, by Zend Technologies with Zend Optimizer v2.5.7, Copyright (c) 1998-2004, by Zend Technologies If you see version 2.5.7 as in the above output, you will need to either disable or upgrade the Optimizer.

2. Install Drupal

CiviCRM currently requires Drupal 5.x. The paths mentioned here are recommended for Drupal 5.x.

If you do not have the required version of Drupal installed, refer to:

• Drupal Installation Guide

  Path for Drupal The rest of these instructions assume that you have Drupal installed in /var/www/drupal. Adjust paths as needed.

Create Folders for Drupal

Create folders with write permissions:

/var/www/drupal/files/civicrm/crm_docs/
/var/www/drupal/files/civicrm/templates_c/
/var/www/drupal/files/civicrm/upload/ 

 Drupal Page Caching Optional Configuration

If you are using Drupal's page caching feature, you will most likely want to modify your settings.php file so that Drupal will not cache CiviCRM pages.  The reason for this is that if Drupal caches your CiviCRM pages, you may have trouble with anonymous users' sessions that could impact CiviContribute and other CiviCRM features.

 Add this code to your settings.php file:  (/drupal/sites/default/settings.php)

$conf = array(
  'file_directory_path' => conf_path() .'/files', // not needed for this, but probably exists
  'page_cache_fastpath' => 1,
);


function page_cache_fastpath() {
if (substr($_GET['q'], 0, 7) == 'civicrm' || substr($_GET['q'], 0, 4) == 'user') {
    global $conf;
    $conf['cache'] = CACHE_DISABLED;
  }
}

• how do i know if page caching is enabled?
  1. Log in as your Drupal site's administrator.
  2. Go to the *Administer » Site configuration » Performance* page.
  3. Check the  Caching mode.

3. Verify or Create Database for CiviCRM Data

CiviCRM may be configured to use the existing Drupal database, or a separate database. All CiviCRM table names are prefixed with "civicrm_" so you should not encounter any table-naming conflicts as long as your Drupal site(s) do not use this prefix. However you may choose to use a separate database for a variety of reasons.

Throughout the documentation we'll be using "drupal_db", "drupal_user", "drupal_password" "drupal_db_server", and "civicrm_db", civicrm_user", "civicrm_password", "civicrm_db_server" to distinguish Drupal database info from CiviCRM database info. If in your case they are the same database, that is okay.

Using existing Drupal database for CiviCRM?

• Verify the drupal_db (database name), drupal_user, drupal_password, and drupal_db_server. Drupal database info can be found in the $db_url variable of Drupal's settings.php file (located by default in drupal/sites/default/).

• Skip to the next step.

Using a separate database for CiviCRM?

• This method is recommended to make upgrades to the Drupal Database cleaner.  Create the database using these steps from the command line. Modify the instructions if you choose not to use 'civicrm' for the civicrm_db and civicrm_user name.

$ mysql -u root -p

// Enter the root user password when prompted.

mysql> CREATE DATABASE civicrm;
mysql> GRANT ALL PRIVILEGES on civicrm.* TO civicrm@localhost
    -> identified by 'USE_A_GOOD_PASSWORD';
Query OK, 0 rows affected (0.02 sec)

mysql> flush privileges;

4. Download and Install CiviCRM Code

All CiviCRM code and packages used by CiviCRM (such as PEAR libraries) are included in the CiviCRM distribution files ('tarballs'). Follow these steps to download and install the codebase:

• Verify your PHP version using either $ php -i from the command line, or by running the phpInfo.php file you created in step 1. above. Remember, CiviCRM requires PHP 5+ and is no longer compatible with PHP 4.x versions.

• Download the appropriate tarball file from here with your browser. Tarball file-names include the CiviCRM version, as well as the source control revision number and the CMS (drupal). For example, civicrm-1.9.11940-drupal-php5.tar.gz is CiviCRM version 1.9 - revision 11940 for Drupal.

• Copy or ftp the tarball file to your server.

  Downloading Directly to Your Server with wget If you have command-line access, you may prefer to download the tarball file directly to you server using wget: // Move into Drupal's modules directory cd /var/www/drupal/sites/all/modules // wget the file (modify this line to use the current tarball file name for the version you want) wget http://downloads.sourceforge.net/civicrm/civicrm-1.9.11940-drupal-php5.tar.gz

• Un-tar (unpack) the codebase into the drupal/sites/all/modules directory.

  // Move to the drupal/sites/all/modules directory (if not already there)
  cd /var/www/drupal/sites/all/modules
  
  // Un-tar the file (modify this line with the actual downloaded filename)
  tar -xzf civicrm_download_file.tgz

• You should now have a drupal/sites/all/modules/civicrm directory with a number of directories below it (including bin, CRM, sql and templates).

  CiviCRM doesn't use the Drupal 5 install file If you are installing on Drupal 5 you may notice in the civicrm/drupal folder a file civicrm.install.sample.  This is an example of how you would write a .install file for civicrm in Drupal 5, but it is unlikely to work with your system unless you know what you are doing to modify this file.  For the time being, it is better to follow the instructions below to manually set up your database tables.  Don't worry: Drupal 5 will load the module quite happily without the .install file being  enabled.

5. Create and Load CiviCRM Database Tables

Verify your MySQL version

• If you have command-line access:

  $ mysql -V
  mysql  Ver 14.7 Distrib 4.1.7, for pc-linux-gnu (i486) using readline 4.3

• If you are using phpMyAdmin, browse to the home page and look for the line below the 'Welcome...' message:
  MySQL 4.1.7-log running on localhost as root@localhost
  This site is running MySQL 4.1.7.

  CiviCRM v1.9 does not support MySQL versions older than 4.1.x

Create CiviCRM database tables and load fixed data (e.g. phone types, default location types, etc.) and sample contact records

This Step Will Destroy Any Existing CiviCRM Data The script which creates CiviCRM tables first drops these tables if they already exist. This script should NOT be run against an existing CiviCRM database unless you want to lose all previous data and start from scratch. You also can NOT use this script for a 'destructive upgrade' from v1.8 to v1.9 due to foreign key constraints - unless you drop your entire civicrm database first. Refer to the separate upgrade documentation for instructions on upgrading existing CiviCRM data.

Using phpMyAdmin from your browser

• Bring up the SQL window for your civicrm_db
• Browse to /var/www/drupal/sites/all/modules/civicrm/sql/civicrm.mysql and click Go (NOTE: In version 1.9 and below, you need to use the file civicrm_41.mysql)
• (YOU ARE NOT DONE YET)
• Next, browse to either:
  • /var/www/drupal/modules/civicrm/sql/civicrm_generated.mysql* (if you want sample contacts, profile forms, events and other data - this provides a helpful head-start to using CiviCRM)
  • OR browse to /var/www/drupal/modules/civicrm/sql/civicrm_data.mysql (if you do NOT want the sample data to be loaded)
• Click Go. You must load either civicrm_generated.mysql OR civicrm_data.mysql.

Using MySQL from the command-line

// Move to the civicrm/sql sub-directory
cd /var/www/drupal/sites/all/modules/civicrm/sql
mysql -u civicrm_user -h civicrm_db_server -pcivicrm_password civicrm_db < civicrm.mysql
mysql -u civicrm_user -h civicrm_db_server -pcivicrm_password civicrm_db < civicrm_generated.mysql

NOTE: In version 1.9 and below, you need to use the civicrm_41.mysql file.

If you want to have a localised CiviCRM install The main "switch" for making CiviCRM localised are the Language and Currency settings controlled from Administer CiviCRM » * Global Settings » Localisation. That said, there are certain "strings" (text pieces) used through CiviCRM that are actually contained in the database; such strings are the location types (Work, Home...), activity types (Meeting, Phone Call...), relationship types (Child of...), etc. If you want to have these strings localised, you will need to import the proper civicrm_data.$locale.mysql for your locale (e.g., civicrm_data.pl_PL.mysql for Poland) instead of the civicrm_generated.mysql file. This will not import the sample data, but will ensure that the provided qualifier strings (e.g. individual name prefixes, location types, etc.) are localised.

6. Edit CiviCRM Configuration File

The CiviCRM configuration file contains important settings which control the database connections and root directory path for your site. CiviCRM will not load properly until these basic settings have been configured. A sample of this file is included in the distribution.

In this section, you will create a working copy of the configuration file and edit the settings to meet your environment and requirements. This procedure assumes a single Drupal 'default' site with a single CiviCRM configuration file. For multi-site Drupal installations, you will have a separate civicrm.settings.php file for each site (corresponding to the Drupal settings.php file for each site). More info on multi-site installations...

• Create your working copy of the configuration file by copying the sample file to the appropriate Drupal sites directory.

  $ cd /var/www/drupal/sites/all/modules/civicrm
  $ cp civicrm.settings.php.sample /var/www/drupal/sites/default/civicrm.settings.php

• Now open the file <drupal_root>/sites/default/civicrm.settings.php in your favorite editor. It should look like this:

<?php
/**
 * CiviCRM Configuration File - v2.0
 */

/**
 * Content Management System (CMS) Host:
 *
 * CiviCRM can be hosted in either Drupal or Joomla.
 * 
 * Settings for Drupal 5.7:
 *      define( 'CIVICRM_UF'        , 'Drupal' );
 *      define( 'CIVICRM_UF_VERSION', '5.7' );
 *      define( 'CIVICRM_UF_URLVAR' , 'q'  );
 *
 * Settings for Joomla 1.0.x and 1.5.x:
 *      define( 'CIVICRM_UF'        , 'Joomla' );
 *      define( 'CIVICRM_UF_VERSION', '1' );
 *      define( 'CIVICRM_UF_URLVAR' , 'task'  );
 *
 * Settings for Standalone:
 *		define( 'CIVICRM_UF'	, 'Standalone');
 *		(Leave out CIVICRM_UF_VERSION.)
 *		define( 'CIVICRM_UF_URLVAR', 'q');
 *
 * You may have issues with images in CiviCRM. If this is the case, be sure
 * to update the CiviCRM Resource URL field (in Administer CRM: Global
 * Settings: Resource URLS) to your CiviCRM root directory.
 */

define( 'CIVICRM_UF'               , 'Drupal'        );
define( 'CIVICRM_UF_VERSION'       , '5.1' );
define( 'CIVICRM_UF_URLVAR'        , 'q'  );

/**
 * Content Management System (CMS) Datasource:
 *
 * Update this setting with your CMS (Drupal or Joomla) database username, server and DB name. Comment it out if using CiviCRM standalone.
 * Datasource (DSN) format:
 *      define( 'CIVICRM_UF_DSN', 'mysql://cms_db_username:cms_db_password@db_server/cms_database?new_link=true');
 */

define( 'CIVICRM_UF_DSN'           , 'mysql://civicrm:civicrm@localhost/drupal_5?new_link=true' );

/** 
 * Content Management System (CMS) User Table-name:
 *
 * Update the CIVICRM_UF_USERSTABLENAME if needed to match the name of the table
 * where the CMS user data is stored. Default for Drupal and Standalone installs is 'users'.
 * If you are using table-prefixing for the users table, you must enter the tablename
 * with the prefix. Default table name for Joomla - 'jos_users'. For Mambo - 'mos_users'.
 */

define( 'CIVICRM_UF_USERSTABLENAME', 'users' );

/**
 * CiviCRM Database Settings
 *
 * MySQL Version:
 * CiviCRM requires MySQL version 4.1 or greater.
 * IMPORTANT: Enter closest dot release to your installed version. 4.1, 5.0 are all valid examples. Do NOT
 * specify minor revision (second dot) - 4.1.2 is NOT a valid value for this setting. 
 *
 * Database URL (CIVICRM_DSN) for CiviCRM Data:
 * Database URL format:
 *      define( 'CIVICRM_DSN', 'mysql://crm_db_username:crm_db_password@db_server/crm_database?new_link=true');
 *
 * Drupal and CiviCRM can share the same database, or can be installed into separate databases.
 *
 * EXAMPLE: Drupal and CiviCRM running in the same database...
 *      DB Name = drupal, DB User = drupal
 *      define( 'CIVICRM_DSN'         , 'mysql://drupal:YOUR_PASSWORD@localhost/drupal?new_link=true' );
 *
 * EXAMPLE: Drupal and CiviCRM running in separate databases...
 *      Drupal  DB Name = drupal, DB User = drupal
 *      CiviCRM DB Name = civicrm, CiviCRM DB User = civicrm
 *      define( 'CIVICRM_DSN'         , 'mysql://civicrm:YOUR_PASSWORD@localhost/civicrm?new_link=true' );
 *
 * MySQL Path:
 * This stores the installed path of mysql. You will need to verify and modify this value if you are
 * planning on using CiviCRMs built-in Database Backup utility. If you have shell access, you may be
 * able to query the path by using one of the following commands:
 * $ whereis mysql
 * $ type mysql
 *
 */
 
define( 'CIVICRM_MYSQL_VERSION', 5.1 );
define( 'CIVICRM_DSN'          , 'mysql://civicrm:civicrm@localhost/civicrm_trunk?new_link=true' );
define( 'CIVICRM_MYSQL_PATH', '/opt/local/bin/' );

/**
 * File System Paths:
 *
 * $civicrm_root is the file system path on your server where the civicrm
 * code is installed. Use an ABSOLUTE path (not a RELATIVE path) for this setting.
 *
 * CIVICRM_TEMPLATE_COMPILEDIR is the file system path where compiled templates are stored.
 * These sub-directories and files are temporary caches and will be recreated automatically
 * if deleted.
 *
 * IMPORTANT: The COMPILEDIR directory must exist,
 * and your web server must have read/write access to these directories.
 *
 *
 * EXAMPLE - CivicSpace / Drupal:
 * If the path to the CivicSpace or Drupal home directory is /var/www/htdocs/civicspace
 * the $civicrm_root setting would be:
 *      $civicrm_root = '/var/www/htdocs/civicspace/modules/civicrm/';
 *
 * the CIVICRM_TEMPLATE_COMPILEDIR would be:
 *      define( 'CIVICRM_TEMPLATE_COMPILEDIR', '/var/www/htdocs/civicspace/files/civicrm/templates_c/' );
 *
 * EXAMPLE - Joomla Installations:
 * If the path to the Joomla home directory is /var/www/htdocs/joomla
 * the $civicrm_root setting would be:
 *      $civicrm_root = '/var/www/htdocs/joomla/administrator/components/com_civicrm/civicrm/';
 *
 * the CIVICRM_TEMPLATE_COMPILEDIR would be:
 *      define( 'CIVICRM_TEMPLATE_COMPILEDIR', '/var/www/htdocs/joomla/media/civicrm/templates_c/' );
 *
 * EXAMPLE - Standalone Installations:
 * If the path to the Standalone home directory is /var/www/htdocs/civicrm
 * the $civicrm_root setting would be:
 *      $civicrm_root = '/var/www/htdocs/civicrm/';
 *
 * the CIVICRM_TEMPLATE_COMPILEDIR would be:
 *      define( 'CIVICRM_TEMPLATE_COMPILEDIR', '/var/www/htdocs/civicrm/templates_c/' );
 */

global $civicrm_root;

$civicrm_root = '/Users/dgg/htdocs/drupal/sites/all/modules/civicrm/';
define( 'CIVICRM_TEMPLATE_COMPILEDIR', '/Users/dgg/htdocs/drupal/files/civicrm/templates_c' );
    
/**
 * Site URLs:
 *
 * This section defines absolute and relative URLs to access the host CMS (Drupal or Joomla)
 * resources. Also you can use Standalone to access the host CMS resources. 
 *
 * IMPORTANT: Trailing slashes should be used on all URL settings.
 * 
 *
 * EXAMPLE - Drupal Installations:
 * If your site's home url is http://www.example.com/drupal/
 * these variables would be set as below. Modify as needed for your install. 
 *
 * CIVICRM_UF_BASEURL - home URL for your site:
 *      define( 'CIVICRM_UF_BASEURL' , 'http://www.example.com/drupal/' );
 *
 * EXAMPLE - Joomla Installations:
 * If your site's home url is http://www.example.com/joomla/
 *
 * CIVICRM_UF_BASEURL - home URL for your site:
 * Administration site:
 *      define( 'CIVICRM_UF_BASEURL' , 'http://www.example.com/joomla/administrator/' );
 * Front-end site:
 *      define( 'CIVICRM_UF_BASEURL' , 'http://www.example.com/joomla/' );
 *
 * EXAMPLE - Standalone Installations:
 * If your site's home url is http://www.examle.com/civicrm/
 *
 * CIVICRM_UF_BASEURL - home URL for your site:
 *      define( 'CIVICRM_UF_BASEURL' , 'http://www.example.com/civicrm/standalone/' );
 */
 
define( 'CIVICRM_UF_BASEURL'  , 'http://localhost/dgg/drupal/' );

/**
 * SMTP Server Authentication Password:
 *
 * If your SMTP server requires authentication, you will enable that and enter the 
 * Username from Administer CiviCRM >> Global Settings >> SMTP. Then enter the
 * authentication Password below.
 *
 */
define( 'CIVICRM_SMTP_PASSWORD', ''    );

/**
 * Multi-site Support
 *
 * CiviCRM uses Domain ID keys to allow you to store separate data sets for multiple sites
 * using the same codebase.
 *
 * Refer to the 'Multi-site Support' section of the Installation Guide for more info.
 */

define('CIVICRM_DOMAIN_ID' , 1 );

/**
 * Joomla! Front-end Component Flag
 * If this configuration file is being used by a Joomla! front-end CiviCRM component
 * instance, set this value to 1.
 */

define( 'CIVICRM_UF_FRONTEND', 0 );

/**
 * 
 * Do not change anything below this line. Keep as is
 *
 */

$include_path = '.'        . PATH_SEPARATOR .
                $civicrm_root . PATH_SEPARATOR . 
                $civicrm_root . DIRECTORY_SEPARATOR . 'packages' . PATH_SEPARATOR .
                get_include_path( );
set_include_path( $include_path );

define( 'CIVICRM_SMARTYDIR'  , $civicrm_root . DIRECTORY_SEPARATOR . 'packages' . DIRECTORY_SEPARATOR . 'Smarty' . DIRECTORY_SEPARATOR );
define( 'CIVICRM_TEST_DIR'   , $civicrm_root . DIRECTORY_SEPARATOR . 'test-new'   . DIRECTORY_SEPARATOR );
define( 'CIVICRM_DAO_DEBUG'  , 0 );
define( 'CIVICRM_TEMPLATEDIR', $civicrm_root . DIRECTORY_SEPARATOR . 'templates'   );
define( 'CIVICRM_PLUGINSDIR' , $civicrm_root . DIRECTORY_SEPARATOR . 'CRM' . DIRECTORY_SEPARATOR . 'Core' . DIRECTORY_SEPARATOR . 'Smarty' . DIRECTORY_SEPARATOR . 'plugins' );

define( 'CIVICRM_GETTEXT_CODESET'    , 'utf-8'   );
define( 'CIVICRM_GETTEXT_DOMAIN'     , 'civicrm' );
define( 'CIVICRM_GETTEXT_RESOURCEDIR', $civicrm_root . DIRECTORY_SEPARATOR . 'l10n' );

if ( function_exists( 'variable_get' ) && variable_get('clean_url', '0') != '0' ) {
    define( 'CIVICRM_CLEANURL', 1 );
} else {
    define( 'CIVICRM_CLEANURL', 0 );
}

// force PHP to auto-detect Mac line endings
ini_set('auto_detect_line_endings', '1');

// make sure the memory_limit is at least 32 MiB
$memLimitString = trim(ini_get('memory_limit'));
$memLimitUnit   = strtolower(substr($memLimitString, -1));
$memLimit       = (int) $memLimitString;
switch ($memLimitUnit) {
    case 'g': $memLimit *= 1024;
    case 'm': $memLimit *= 1024;
    case 'k': $memLimit *= 1024;
}
if ($memLimit >= 0 and $memLimit < 33554432) {
    ini_set('memory_limit', '32M');
}

?>
...
?>

• Review the following sections and associated explanations carefully, and modify the values as needed:
  • Content Management System and CMS Datasource
  • CiviCRM Database Settings
  • File System Paths
  • Base URL
    Pay special attention to getting all the values and trailing slashes right in this file!

• Most other configuration settings are controlled from the CiviCRM administration menus ( *Administer CiviCRM » Global Settings* ). Refer to the online help for each of these settings screens for more information.

• Save your civicrm.settings.php in <drupal_root>/sites/default/ directory.

7. Enable CiviCRM Module and Blocks

Now you are ready to log in to your Drupal installation (with an adminstrator level login) and enable the CiviCRM module and blocks.

• Go to Administer » Site Building » Modules.
• Make sure CiviCRM is enabled (CiviCRM is listed under "Other").
• Click Save configuration at the bottom of this form.
  Note that Drupal tries to create the /files/ directory (and make it writeable), but only when saving admin/settings. Same holds for /temp directory, and a /uploads/ directory in the CiviCRM module root. On a brand-new Drupal install, this directory may be missing. Even on an existing installation, if file permissions are not set properly, the directory may be missing. If enabling the civicrm module generates errors regarding the files directory, you must create it (writeable) manually. Refer to Step 2 for instructions on directories to create and permissions to set.

• Go to Administer » Site Building » Blocks and enable CiviCRM blocks by assigning them to a Region (typically the left sidebar - but this depends on your theme and desired layout). Blocks to consider enabling are "CiviCRM Menu", "CiviCRM Quick Add", "CiviCRM Search" and "CiviCRM Shortcuts". In order to get a handy layout of left-hand menu items, you could also assign weights to the blocks as follows:
  • Menu Weight: -4
  • Search Weight: -3
  • Shortcuts Weight: -2
  • Quick Add Weight: -1

• Go to Administer » User management » Access control
  • Verify that the Roles that you want to have access to CiviCRM have the appropriate permissions checked. CiviCRM is installed with a number of fixed permissions (such as "edit contacts" and "administer CiviCRM").

    Permissions for the Anonymous Role Many sites want anonymous visitors to have access to certain CiviCRM functionality. Consider enabling these permissions to the Anonymous role - depending on your requirements: make online contributions : If you plan on soliciting online contributions from visitors, enable this permission for the "anonymous" role. register for events : If you plan to use CiviEvent and want to allow un-authenticated visitors to register for events online - enable this permission for the "anonymous" role. access all custom data : If you plan on collecting "custom" data from visitors in standalone forms or as they make a contribution - enable this permission.

8. Create CiviCRM Contacts for Existing Drupal Users

Once installed, CiviCRM keeps your Drupal Users synchronized with corresponding CiviCRM contact records. The 'rule' is that there will be a matched contact record for each Drupal user record. Conversely, only contacts who are authenticated users of your site will have corresponding Drupal user records.

When CiviCRM is installed on top of an existing Drupal site, a special CiviCRM Administrative feature allows you to automatically create CiviCRM contacts for all existing Drupal users:

• Login to your Drupal site with an administrator-level login
• Click the CiviCRM link in the main navigation block
• Click Administer CiviCRM
• Click Synchronize Users-to-Contacts in the top group of icons

9. Test-drive CiviCRM

There should now be a CiviCRM link in your Drupal menu. Click that link and the CiviCRM Menu, Shortcuts, Search and New Individual Blocks should appear.

You can now explore CiviCRM end-user features and begin configuring CiviCRM for your site/organization needs. Refer to the Administrator Guide for information on configuration tasks and options.

Trouble-shooting Resources

Review the Installation and Configuration Trouble-shooting section of our wiki for help with problems you may encounter during the installation.

Installing the CiviCRM Codebase in a Non-default Location If your CiviCRM codebase is NOT located in either <drupal root>/modules/civicrm or <drupal root>/sites/all/modules (i.e. you are using a symlink from there to your codebase) - you will need to create a local file in the top-level directory of your codebase which points to the location of your drupal sites directory. // Create a new file - settings_location.php // Enter the following code (substitute the actual location of your // <drupal root>/sites directory) <?php define( 'CIVICRM_CONFDIR', '/home/lobo/public_html/drupal/sites' ); ?> Some symptoms that indicate that this file is needed are: Calendar widget doesn't work (throws a Javascript error) CiviMail scripts for open tracking, SOAP authentication, etc. don't function.

You can often find solutions to your issue by searching the installation support section of the community forum OR the community mailing list archives, and you can check out the Installation section of our FAQs.

If you don't find an answer to your problem in those places, the next step is to post a support request on the forum.