Keying off of the work we did previously with EGA, we saw an opportunity to improve on grants management in CiviCRM by using VBO to flag grants.

Code sprints are a great way to work on pet projects, new features, crusty bug fixes or glorious UI improvements. Often times, a code sprint will have a goal and anyone that wants to attend the sprint should try to work towards that goal.

This case study was written by Eliet Henderson, the Development Director at San Francisco Baykeeper, a small nonprofit organization dedicated to protecting San Francisco Bay from pollution. Baykeeper has an annual budget of $750,000 and eight staff members, two of which handle outreach, communications and fundraising.

If you're running a Drupal/CiviCRM site where members have Drupal user accounts, you may find yourself in a situation where you want to expose CiviCRM data on a Drupal user page. We like to use this technique when we've pushed all of the member information into the CiviCRM contact, so the only thing specific about the member on the Drupal side is their username and role.

As part of an ongoing project with Environmental Grantmakers Assocation (EGA), which involves moving them off of a series of disparate databases to Drupal/CiviCRM, we developed a solution that allows them to track grants from a 3rd party perspective.

We're excited to see even more adoption of the discount module we've been developing. The CiviCRM core team has proposed a Make-it-Happen to bring event and membership discounts to CiviCRM 4.1. If the goal is reached, discounts will be an integral part of CiviCRM and not just a Drupal module.

One of our clients reported a problem of stalled contribution pages after clicking submit. The page would simply timeout and give back a not-so-friendly HTTP 500 error. After a bit of debugging and banging heads against the wall, we asked dlobo for a bit of help on IRC. 20 minutes later, he traced the bug back to CRM/Member/BAO/Membership.php and generated a patch against 3.4.

The CiviCRM discount module we've been working on over the last couple of months has reached a new milestone. We've added the ability for discount codes to be purchased via Ubercart.

Profiles can be used to collect and expose data from CiviCRM. One common scenario is to display a membership directory. Recently, one of our clients wanted to use several different profiles to present different aspects of their membership directory based on groups, tags and a few custom fields.

We've been working with one of our clients to rebuild the way they capture membership information, both new and renewing. One of the requirements is to allow potential members to signup for access to forums, comments, subscriptions, etc. The goal is to provide the user with a smooth, logical process to create an account and if they choose, to become a member.

As we implement a few remaining tweaks and features in anticipation of a "1.0" stable release to the CiviEvent Discount module, we reflect on the last ~6 weeks.

In the process of improving Drupal/CiviCRM performance for a client, we discovered that CiviMember Roles Sync was killing the database every 15 minutes. Digging into the LAMP stack and analyzing the workflow for the organization, we learned they set the sync to Drupal cron out of necessity.

We're working on a module to generate discount codes for events in CiviCRM. It's still in early development but it should be useful enough to play around with. We recommend waiting for a stable release before deploying it into a production environment for real events. A recent feature we added was the ability to set monetary or percentage based discounts.

We recently came across an odd problem with CiviReport. Every once in a while (hint, hint) CiviReport would display 0 results even though the smart group it was referencing did in fact have contacts.

With the help of a new co-maintainer (thanks AJA), we've consolidated all the patches for uc_civicrm and moved them to Drupal. This allows us to better maintain version releases, issues, documentation, etc.

The uc_civicrm module that integrates Ubercart with CiviCRM has been updated to support CiviCRM 3.0.2 and Ubercart 6.x-2.2.  You can download it here.

Introduction: The Need

Progressive Technology Project (PTP) supports grassroots community organizing groups nationwide that engage in social, economic and environmental justice efforts to empower low-income people and communities of color. These groups conduct phone banking and field canvassing as an integral part of their base-building and voter engagement strategies to engage existing and new constituents. PTP hired Dharmatech to help them build PowerBase: a customized CiviCRM for use by community organizing groups.

FileMaker is a popular "personal database" package that runs on the Windows or Mac desktop.  Many organizations keep their data in a FileMaker database.  Because of the limitations of this method of maintaining a database, some organizations wish to migrate their database to CiviCRM.  This article describes the obstacles in doing that and how to overcome them.

We recently had a client that needed to allow anonymous users to update CiviCRM data. No problem right? Right! As long as those anonymous users aren't updating optional fields. This post is here for historical reasons. If you're using a fairly recent version of CiviCRM (3.x), you don't need this module.

Attachments: 

civicrm_profile_tweak-6.x-1.x-dev.tar_.gz