This wiki was made redundant by CiviCRM Extensions & Modules for Drupal.
Not sure that this page is really useful, it will always be out of date compared to:
Great White North Office
Personally (and professionally) I hate using the search feature on Drupal with the 4,303 results on a search for the term civiCRM. I would much rather go to a page with a handful of modules and succinct descriptions of why they belong on that page. If it is maintained (and that's a big if) then it will always be the first place I would look.
Drupal Developer at Nomensa, and part-time freelancer.
I stopped updating this wiki when I found this page of documentation for CiviCRM Modules and Extensions that @choster started last month. Best list I've seen... and not just because it included most of the modules I've been working on :) The only thing I'd like to add are the versions supported... and I don't think it really belongs under Social Networking and Collaboration -> Community building and social networking modules.
@dalin, I'm going to have to agree with @awasson. Drupal.org's search isn't that useful since it includes any mention of CiviCRM in the description including several modules that say using it is "better than CiviCRM because...".
Part of the reason I'm looking at CiviCRM related modules is I'm looking at adding modules to http://drupal.org/project/civicrm_starterkit. While trimming down the official CiviCRM download and replacing GPL packages that can be downloaded separately, we're still waiting on an official, minimized 4.2 download. Once that is available, the starter kit should be the easiest way to install CiviCRM on Drupal.
While I'm excited to see the progress being make of the Drupal native CRM solutions like ThinkShout's RedHen and Trellon's CRM Core, my initial impression of these projects is they have a long way to go before they match up feature for feature to CiviCRM. Even after these project mature, I'm not sure when I'd recommend managing an organization's CRM entirely in a CMS. The thought of linking a CRM to Drupal's upgrade cycle makes my head hurt. The level of integration between CiviCRM/Drupal has really improved with additional Views support and Rule. Where it's at now seems about right to me... and even where I've found it lacking, I've been able to write something to solve the problem. Starting the CiviCRM starter kit motivated me to commit several modules I'd written and used on a few projects, but hadn't cleaned up to the point they'd really help anyone else.
Any thoughts on starting a section of documentation for CiviCRM/Drupal integration under http://drupal.org/node/1256910?
I'm not suggesting reproducing the documentation available at http://wiki.civicrm.org/, but simply consolidating the documentation for modules that can be added to Drupal beyond what's included in the core CiviCRM modules.
Good ideas guys, we also need to make sure we include some of the CiviCRM native extensions that are popping up here and there to…
hey kevin and folks:
Starting in 4.2 we've made a strong commitment to providing a more complete extensions directory. Tim Otten is working on this along with the kasia and folks at freeform.ca
We'll announce this with the 4.2 release. Its a couple of weeks from being launched.
We hope to include all existing drupal modules and the newly created independent extensions
I think all the bugs have been worked out, so here is the CiviCRM Extensions & Modules for Drupal @lobo referred to.
I'm not sure if accounts need to be in a specific role on civicrm.org to add extensions and related releases. Since several people have started adding extensions, I'm guessing most people will see the option to add these when they login and go to http://civicrm.org/node/add
My feedback so far has been that the process for changing node owners needs to be obvious. Currently anyone can add a module or extension to the directory... which is good to get started, but I've already had to ask to get ownership of nodes to update modules I maintain. And I've added modules to the directory that I don't maintain.
The process for adding release is a very manual process at this point, so instead of linking to the specific .tar.gz or zip, I'm linking to the module's project page. That way if I forget to update civicrm.org when I role a new release, someone seeing the release on http://civicrm.org/extensions/drupal is more likely to get the most recent version and see any warnings, notices, etc that I've added to the project page.
It would be great if Drupal/CiviCRM developers could register their modules themselves so they can make updates. It looks like most of the maintainers on @choster's list are members of this group. I'd like to suggest giving everyone a week to register their modules/projects themselves. If there are modules missing next week, feel free to give the maintains a nudge with an issue in the queue. If there are still modules missing after that, then anyone should feel free to add them and the maintain can request the node ownership be changed later.
As Kevin mentioned, we are putting the finishing touches on the new (and long overdue) extensions directory on CiviCRM.org. Thanks to Kasia Wakarecy and the folks at Freeform.ca for their amazing work making the directory a reality.
Along with the directory, we are rolling out the 4.2 release early next week with an automated distribution and installation feature for native CiviCRM extensions. This functionality was basically alpha-level in 4.1. For 4.2, we've put a lot of effort towards putting together the missing pieces - and we're hopeful that this will really accelerate sharing and collaboration. CiviCRM native extensions will have (nearly?) equivalent capability to extend Civi as Drupal modules do for Drupal - including the ability to define their own forms, screens, schema and full use of the hook system.
You need a CiviCRM.org login to submit an extension, but no special role is required. Please consider taking a few minutes to explore the directory and then submit any of your currently supported modules or extensions that you think would be useful to others in the community!
See all hot content.
Drupal is a registered trademark of Dries Buytaert.