Integrations

This module is being supported for Drupal 7 and maintained for security issues

Exposes Salsa objects as entities to Drupal. Doing that allows close integration with various modules like Rules and Entity Reference.

The goal is to replace the public user interface of Salsa CRM completely, integrate it neatly into a Drupal website and allowing customizations through standard Drupal API's and concepts (e.g. hook_form_alter()).

Features

(Work in progress, not everything is completely working yet)

• Exposes a growing list of salsa objects within Drupal, including but not limited
  to:
  • Supporters
  • Groups
  • Signup pages
  • Donate Pages
  • Questionnaires
  • Tell a friend pages
  • Events
  • Petitions
  • Targeted Actions
  • Unsubscribe pages
• The pages are displayed as forms which are then submitted to Drupal and the necessary actions are made through the API
• All fields (including custom fields) are exposed as Entity properties
• Rules integration
• Entity reference integration, including support for the autocomplete widget

description of module testmodule

A little plugin into the Subscriptions framework.

Developers (or anyone via a variable_set, and soon administrators through the UI) can use this module to do either or both of these things when a post is published:

• Subscribe users who are referenced in a userreference field.
• Subscribe all authors of nodes belonging to a referenced taxonomy term.

The term reference part can automatically subcribe users to updates on a node if they have authored content in a taxonomy term that is referenced via a taxonomy term reference field.

The user reference part can automatically subscribe users who are in a References module user reference field.

Currently, what field instance this applies to needs to be set as a variable holding an array with one or more arrays with the keys entity type, bundle, and field name. Soon, which field instances trigger this will be configurable by the administrator in the user interface courtesy a separate UI module.

To configure in code, an update hook such as the following will work:

<?php
function hook_update_7001() {
variable_set('subscriptions_referencedusers_term', array(array('entity_type' => 'node', 'bundle' => 'case_presentation', 'field_name' => 'field_expertgroup')));

CiviCRM Multiday Event creates multiple entity based events associated to a single Drupal node linked to a single CiviCRM Event. The duration of the CiviCRM Event last from the start date and time of the first session to the ending date and time of the last session. So if you have a class that meets every Friday in May, Drupal will display 4 events (5/4, 5/11, 5/18, and 5/25). CiviCRM will only have 1 event running from 5/4-5/25. This allows groups already leveraging CiviCRM for event registration, payment, reporting, and certifications, to continue using those components while making it easier to display individual events with Views.

Screencast: Beardcast #3 - CiviCRM Mulitday Event w/ a Don Quixote Looking Mustache and Goatee

This module will address 3 common problems with Events in Drupal/CiviCRM integrations:

1. Display a CiviCRM Event with multiple dates in a Calendar
2. Display CiviCRM Events and other Drupal events in the same Calendar Views
3. Importing Events into CiviCRM (Now use Feeds!)

Examples:channelAustin's Training Calendar w/ Color Coded Class Types

Heidelpay integration for the Drupal Commerce