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

This section contains a prior version of CiviCRM Documentation. Go to Documentation Home for all current topics.

CiviCRM Documentation (OBSOLETE)

Installing and Upgrading

CiviCRM can be hosted inside the CivicSpace/Drupal OR Joomla! / Mambo content management systems. This section covers automated and manual installs for each environment, as well as detailed procedures for upgrading to the latest release.

Organizing Your Data

An overview of the features available in CiviCRM for organizing your contact data. This section includes descriptions of Tags, Notes, Groups, and Relationships - and provides real-world examples.

Quickstart Guide

What you need to do to quickly configure and start using CiviCRM.

Administrator Guide

These documents cover administrator tasks for setting up a CiviCRM site. This includes configuring tags and relationship types, creating and managing groups, and adding custom data fields to meet the needs of the site's users.

CiviContribute Guide

Documentation on set up and configuration for CiviContribute - the online contribution processing and contributor management component.

CiviMember Guide

Documentation on set up and configuration for CiviMember - the membership management component.

End-user Documentation

End-users use CiviCRM on a day-to-day basis for specific tasks.


This section contains step-by-step 'recipes' for accomplishing special tasks, such as... How can I create a Drupal user for each CiviCRM contact?

Case Studies

Real-life tales from folks who are using CiviCRM.

CiviCRM Public APIs

Detailed documentation for module developers who need to interface with CiviCRM via API calls. Includes links to implementation examples.

CiviMail Configuration


Developer Documentation

Additional topics for core and external module developers, including framework information, localisation details, coding style guidelines...

Notes on Documentation Platform and Objectives

CiviCRM documentation will be initially developed in this section of our Confluence 'wiki'. We are evaluating whether the documentation should be ported to DocBook or a similar open format once we have a completed draft. However, for now Confluence provides a good collaborative authoring environment - as well as the ability to export the documentation to a PDF file or a set of HTML files.

Administrator and End-user Documentation is being structured so that it can be browsed as a 'manual' AND also used to link specific pages directly to the application screens for context-sensitive help.

  • Aucun
  1. Sep 18, 2005

    Elin Waring dit :

    I wanted to make a comment about installation with mambo. Apparently the databasename, password, username, livesite are hard coded in the civicrm files. It would be much better if they would just pick up these variables from mambo.
    This came up because I moved my site, got a new database etc. Civicrm completely stopped working and generated a lot of warings and errors. Eventually I figured it out, but not without a lot of difficulty along the way.

  2. Sep 19, 2005

    civicrm tries to be cms-independent. (we operate with the same code base on drupal and mambo). During the mambo install, we pick up the db name/password from the mambo variables and use them in civicrm. trying to do this dynamically is possible, but is a bit more burdensome on the core code (and also requires different versions for mambo/drupal etc) which we'd like to avoid


  3. Jun 14, 2006

    Elin Waring dit :

    But couldn't they be hashed?

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.