It was a great gathering of people from different backgrounds showing up for the meetup. By far this was one of the biggest meetups (30+ people) that I have attended. Nice to see the growth in the SF Bay Area civi community!
Meetup kicked off with a report back by Dave Greenberg of the CiviCRM team from CiviCon Chicago. He reviewed growth trends for the platform, and broad goals for the project going forward. You can download Dave's slides as well as most of the other CiviCon Chicago presentations here. This was followed by presentation by Arthur Richards from Wikimedia Foundation. He briefed everyone on how Wikimedia uses CiviCRM to manage 999,350+ contacts and 1,067,739+ contribution records. Arthur's presentation can be found...Read more
Rooty Hollow is excited to announce the release of our Constant Contact Integration module for CiviCRM. If you are not able or willing to deal with sending bulk e-mails form your host this module is for you.
- Upload contacts from a CiviCRM installation...
Many non-profits live and die by the grant money that they are able to bring in. CiviCRM can currently track incoming grant applications through CiviGrant, but there is no way to track outgoing grants applications.
This functionality has been requested by users of CiviGrant in the past, but the project never moved forward. The organization that I work with is very interested in tracking our grant application workflow, which in turn makes me very interested in implementing this functionality.
After some discussion in the forums, it was suggested that I write up a blog post with a few ideas on how to go ahead with the project. Essentially, I see three options:
- Extend CiviGrant by adding DB fields.
- Extend CiviGrant by leveraging activities.
- Replace CiviGrant with a CiviCase workflow.
Before moving ahead, I would like to...Read more
The webform module is a great way to collect info from your contacts, perfect for things like application forms, surveys, contact forms, feedback forms, etc. The hard part is getting those form submissions to actually link to your CiviCRM contacts... until now.
Until now, getting your webforms to work with CiviCRM was a little like Groundhog Day. You wake up in the morning, create the usual form (First Name, Last Name, Address, City, State, Zip, Phone Number, Email, etc.). An hour later, you're done with the easy part. Now you have to write a custom PHP script to intercept those form submissions, call up the Civi APIs (go A team!), and start trying to match up field keys to API $params. It's kind of tedious, and doesn't always work the first time (was it supposed to be 'prefix_id' or 'individual_prefix' or 'individual_prefix_id'?). But a few hours and a few dozen test submissions later you've got it all working. Now...Read more
Since Target Integration released CiviSync - CiviCRM Outlook Synchronization Addon in April this year, I have seen a lot of people asking about it and thanks to those who tested it and provided their feedback. Initial CiviSync was developed for CiviCRM version 2.2 and Outlook 2003/2007.
Based on your feedbacks and the updated requirement from our clients it is time that we need to update the component again but as we all know that CiviCRM has changed big time since version 2.2. The REST API has matured very well and is now very much available to test and use which will ensure that we don't need to put/include nuSOAP in the latest version. Also, Outlook 2010 has been released as well. Outlook 2003 and 2007 development was based around Visual Studio Tools for Office (VSTO) Version...Read more
Check out the PowerPoint presentation for a review of Drupal modules for CiviCRM http://wiki.civicrm.org/confluence/download/attachments/33129543/Drupal+Modules+for+CiviCRM+Drupal+Camp+Toronto+2010.ppt?version=1&modificationDate=1288060322608.
I covered the ones in the tarball as well the ones on drupal.org that have stable releases for Drupal 6 and reasonable usage figures. A video of the presentation was recorded along with the rest of the main sessions at the conference. When they are processed and it is put up somewhere I'll update this post with the link.
As background, Drupal Camp Toronto 2010 was a successful two day Drupal camp with over 250 attendees (last one had less than 160) and over 15 sponsors. Keynote speakers included Dries Buytaert from Acquia, Jeff Eaton from...Read more
Getting the Data InCreating a case for a new prospective student is simple: just log in to... Read more
Today at the Bristol Code sprint a few of us made a concerted effort on getting making Giftaid 'plug and play' for Civi.
Our starting point is code written by Millertech and our aim is to get it into a state that we can package it as a Drupal module. Once we've done that, we're hopeful that we'll be able to package it for Joomla also.
We're having to make a few improvements to Civi's hooks, and some modifications to the existing functionality to enable us to package it up, but the benefits are obvious: much easier installation and thus wider uptake of the module, and thus higher CiviCRM adpotion in the UK :)
We spent most of the morning familiarising ourselves with the code and discussing the necessary changes we would need to make. This threw up some difficult problems (I'll spare you the details) but the result was this outline of...Read more
Slight change in plans - I was promising the recipe on packaging payment processors, but we'll do custom reports first. They are second in the hierarchy of complexity after custom searches, and they smoothly introduce small new concept that will be described below.
Again, you need the very custom report first - a php class, as it is handled right now. Usual custom report is made of PHP class and the template. Once we have it, we can go ahead and package it.
In order not to repeat the information which was already described on packaging custom searches, here's quick summary:
prepare the info file (see the sample file at the end of this blog post). The key that we'll choose is: org.civicrm.report.grant
Continuing the series, let's look at packaging payment processors. Before digging in the text below, make sure you're up to date with previous blog posts: on info file format and on packaging custom search.
We'll start as previously, by creating a directory named exactly the same as unique key that we're choosing for our extension. Let's use example of Google Checkout payment processor - both the key and the name of directory will be org.civicrm.googlecheckout.
Now, we need to create the info.xml file. Since this process has been described in detail before, going straight to final effect:... Read more