CiviCRM - Drupal Integration Modules

From DevSummit
Revision as of 21:58, 15 May 2015 by Vivian (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Facilitated by CiviCRM Core Team

This session is designed for developers and techies who want to learn more about options for integrating CiviCRM with Drupal. Topics may include:

  • Drupal user / CiviCRM contact - what's the connection?
  • Integrating CiviEvents with Drupal Calendar
  • Using Views2 to expose "all kinds" of CiviCRM data
  • Connecting Drupal roles to CiviCRM membership and / or groups
  • CiviCRM and Organic Groups integration

Session Notes

CivCRM/Drupal Integration

- Integration
- Customization

Views integration - probably one of the reason that Drupal has gained such adoption.

Allows you to query all nodes and fields within nodes - draw together a collection of those nodes. Specify what fields you want to return, sorting, filtering, etc.

A lot of modules that support views integration. It's relatively easy to expose your custom fields in a module to views. From the beginning - have an admin configurable way to exposed data. Using profile - it aggregates fields. View of individual records, or groups. Set up to expose contact records - but there are others that can't be exposed. And it's not as flexible.

Whole new level of ways to expose data and link with content. Views is very themeable. VIews is nice to show theme information.

If you can get the data to views, then you can use it - for example, mapping, etc.

All pages are rendered by drupal. You can override CiviCRM templates - if you want to customize the appearance. Drupal theme will influence the appearance. Sometimes the CiviCRM classes adapt to the theme, and sometimes not. You can override css with custom css.

Pretty easy to make a seamless appearance so that everything looks the same. How do you have an interface that is recognizable but malleable - within the different CMS systems that CiviCRM is running in. in 3.2 - redoing css, hopefully wlll have to do less customization.

Event registration page - changes in markup. Templating system is Smarty.

Other integration modules - CiviCRM member roles. Control access to content on site based on civi member roles. Group roles - relate groups to roles. And organic groups sync.

Idea: Have canned views to put into the CiviCRM installation for some specific things (members or events, etc.)