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

CiviEngage Installation

Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

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

Documentation Search

CiviCRM 3.2 Documentation

Support and Participation

Developer Resources

CiviCRM book!

Make sure to check out Understanding CiviCRM as well! You can also support this project by ordering a hard copy.

These instructions cover installing and configuring CiviEngage module. The module requires CiviCRM 3.1 or higher.

1. Download and install a copy of CiviCRM 3.2 (or higher). OR upgrade an existing test site to 3.2 (or higher).

2. Checkout the following directory / files from the CiviCRM public repository to the modules directory of your Drupal installation:

3. Set OR verify your CiviCRM SITE_KEY value in civicrm.settings.php:

4. Import custom data in CiviCRM specific to CiviEngage using the following URL:

example URL for browser, assuming drupal directory is /var/www/drupal. Please fix the file path to match your system location

5. Navigate to Drupal Administer >> Site Building >> Modules and enable the CiviEngage module. Click Save.

6. Navigate to Administer CiviCRM >> Configure >> Global Settings >> Address Settings and enable Street Address Parsing by checking that box in Address Editing section. This feature allows you to automatically parses addresses during contact import.

7. Navigate to the CiviCRM Administer menu -> Configure -> Global Settings -> Search Settings -> Autocomplete Contact Search. Uncheck Email and check Phone Number. This makes the phone number available for batch update screen and contact autocomplete widgets.

8. Create three new subtypes for Individual Contacts: Media Contact,  Elected Official and Funder.

9. Create one new subtype for Organization Contacts: Media Outlet

10. Test out the module / reports:

  • Check that expected custom data groups and fields are present
  • Check that expected profiles / profile fields are present
  • Check that extended Demographics (Primary Language, Secondary Language, etc.) are editable and displayed within core Demographics pane (Contact Edit / Contact Summary)
  • Test Address Parsing by adding addresses, saving, going back to edit address and clicking 'Edit Address Elements' to verify proper parsing of street address into street number, street number suffix, street name, unit.
  • Create one or more report instances for the Phonebank List and Walk List report templates.
Labels
  • None

Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.