CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Drupal Modules (Moderator: Donald Lobo) »
  • Details on Drupal integration - WRT flexibility & customization
Pages: [1]

Author Topic: Details on Drupal integration - WRT flexibility & customization  (Read 1180 times)

kentr

  • Guest
Details on Drupal integration - WRT flexibility & customization
July 07, 2009, 02:33:37 pm
Hi,

Are the CiviCRM modules built on top of Drupal's CCK and user profiles, etc?  I'm wondering how much flexibility I'll have while staying within the Drupal system when adding custom fields, integration with other modules (like CCK calculated fields), etc.

Thanks!

Matt2000

  • I post frequently
  • ***
  • Posts: 288
  • Karma: 27
    • http://www.ninjitsuweb.com
Re: Details on Drupal integration - WRT flexibility & customization
July 07, 2009, 03:30:27 pm
No, they are not. CiviCRM uses it's own DB Layer (PEAR:DB), Forms (QuickForm) Presentation layer (smarty), Access Control, etc. It does not use Drupal's APIs for these things.

However, CiviCRM does include an API that makes it possible to write code to synchronize data with Drupal modules, and includea few module sot do this, E.g., Role sync, and Organic Groups sync. There is also a relatively new CCK field type module that exposes CiviCRM contacts. CiviCRM also provides Views integration.
Drupal/CiviCRM micro-blogging http://twitter.com/matt2000

Ninjitsu Web Development http://www.NinjitsuWeb.com/

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Drupal Modules (Moderator: Donald Lobo) »
  • Details on Drupal integration - WRT flexibility & customization

This forum was archived on 2017-11-26.