CiviCRM obsolete?
lefnire - July 17, 2008 - 04:33
I'm going to create a members-directory site: one with all sorts of profile extras, event registration, etc. It seems like the perfect candidate for CiviCRM, but it doesn't seem too difficult to implement using some basic views, node_profile, calendar + event, and the like.
I guess my question is... is CiviCRM easily replicable using modules? Seems that way would make for easier integration with other Drupal modules, since Civi is kinda it's own island in a Drupal install... pros/cons?
As always, it depends on
As always, it depends on your requirements.
Easily replicable using modules? Definitely not... I would be shocked if you could replicate CiviCRM with modules and 50 developers over 6 months. That's becuase CiviCRM handles quite a few big buckets of functionality for you. At the same time, folks have been saying for 18 months that you could build a CRM system with CCK. I still haven't seen one.
Pros:
For a light solution with very limited functionality, modules are a good option.
For a solution built by expert Drupal folks, modules are a good option.
Cons:
For a solution that works "out of the box" modules are a poor solution.
For handling CRM data -- data records that need to be segmented, managed and reported on as data, modules are a poor solution.
For tight integration between data, display and payments, modules are a poor solution since there would be significant integration work to be done at the code level.
For a solution that expands over time (e.g. you need it to do more latter), modules are a poor solution.
Finally, there is a fair amount of work going on with views 2... if we can successfully have views manipulate CiviCRM data, I suspect most of the serious issues are mute. Currently you need to use CiviNode to expose your data to Drupal in a node-friendly way.
Finally, for a members only site, there was recently released a key module.. can't remember exactly what it was called, though.
David Geilhufe
Try CiviCRM!
Wow, fast response & great
Wow, fast response & great input, thanks! Good to know about CiviNode, 'cause that ballpark was where I was a bit concerned.
Yeah, I was originally thinking of CiviCRM vs CCK-CRM as the difference b/w Audio.module & views + embedded_media_field, or as the difference b/w Image.module & views + image_field. In those cases the "out of the box" to "customized solution" gap isn't all that big; however, if it's a dramatically larger gap with Civi vs CCK, then I'll just stick with Civi.
Per chance that "key module" you mentioned... is it a Civi-related module?
Web development & design podcast
The module is
The module is http://drupal.org/project/civimember_roles
David Geilhufe
Try CiviCRM!