Progressive Technology Project (PTP) runs PowerBase, a fully hosted and supported version of CiviCRM for community organizing groups in the United States. PTP has been deeply involved in CiviCRM's expanding functionality through CiviEngage and CiviCampaign and now has commenced a project to improve CiviContribute to strengthen it for grassroots fundraising. While CiviContribute has the basic parts necessary for fundraising, it lacks some of the higher reporting pieces that dedicated fundraising applications have.
Our team has been working with a grassroots fundraising expert and together we identified that the first step would be to provide more dashboard charts for CiviContribute that will allow new users to leverage reporting intelligence with minimal training.
There are several new reports designed to identify the renewal rate of donors or members over time; the lapsed and recovered...Read more
An organisation I work with wishes to extend the Personal Campaign Page (PCP) to allow teams to raise money either using their group PCP page, or individual PCP pages of each team member. In other words, the team organiser creates a PCP page and sets a team objective. The organiser then invites members to join its group. By doing so, the team member creates its own PCP page with a personnal objective.
In terms of functionality:
- Donors can donate either to the team member's page, to the team page, or to the general contribution page.
- The team PCP page should list the members of the team, and how much money they have raised.
- The team PCP page objective should also include the total amount raised by the team (e.g. donations to the group + to team member pages)
This is similar in many ways to the FPWR Fundraising Platform (...Read more
Greetings from Apeldoorn at the Netherlands CiviCRM Code Sprint. I've spent the last several months meticulously working with the fundraising team at the Electronic Frontier Foundation (EFF) to build donate pages that look and act beautifully, remove friction from the donation process, and leverage premiums to get bigger donations.
At the England and Netherlands code sprints after CiviCon London I spent most of my time building a lot of the functionality that I've made for EFF into CiviCRM Core and updating the default contribution page templates. These new contribution pages will be part of the 4.3 release.
I'll start with screenshots from a contribution page in 4.2. Here is the header and some price sets, where you get to choose your amount, choose if you want to make a one-time contribution or a recurring one, and enter your email address:
If you are using Authorize.net as your payment processor (or your clients are) for either one-time payments or automated recurring payments, then my guess is that like me you probably dread the phone call from a bookkeeper such as
"I found some Authorize.net transactions that went through and the money is in the bank, BUT there is no record of the contribution in CiviCRM. What happened?"
Researching these types of issues is very challenging because Authorize.net will never resend a Silent Post URL message, and the logging in CiviCRM about each message ( processed normally, or in error) is rather thin. As a tool to help research these issues, Pogstone Inc. created an enhanced logging feature where every silent post URL message is immediatly logged to a database table and a text file, before the message is processed. We also created a new custom search to query the new table. You can download the files needed...Read more
Vanco Payment processor
BackOffice Thinking is pleased to release the Vanco payment processor to the CiviCRM community. Today we are releasing versions for 3.4x and 4.1x and hope to have a 4.2x version shortly.
This processor allows single payment and recurring for credit cards and ACH (electronic check)
The Vanco payment processor is quite popular among religious organizations and we have been utilizing this processor for past 2 years with many of our clients. Thanks for all the support from the Vanco team along way.
The files, including detailed instructions, can be downloaded here.
The installation is more involved than other...Read more
I am starting a project that will allow CiviCRM to support the needs of an Australian non-profit. This non-profit is subject to the Australian Goods & Services Tax rules (GST) for some but not all transactions.
The GST requirements apply whenever the non-profit provides a tangible good or service in exchange for a payment. This is most common with their dinners, selling DVDs, and items from their gift shop.
I have written up the requirements and possible approaches on the CiviCRM wiki at:
I would love to get feedback from anyone who would like to participate or later use the new module.
At the April sprint, several of us discussed improvements to CiviCRM’s soft credit functionality. For those of us who use CiviCRM for fundraising, soft credits are vital component of managing donor relationships, and there are several ways CiviCRM could be improved to make soft credits more robust and easier to use.
Thanks to Kellie Brownell and Jane Hanley for their contributions to this blog post.
What’s a soft credit? Soft credits allow you to indicate that a second contact has a relationship to another contact’s contribution. Soft credits show up on the soft-credited donor’s Contribution tab in a table below the “hard credit” contributions.
When are soft credits used? We came up with a number of different use cases for soft credits (and there are probably others):
Facilitator credits. When someone helps facilitate a contribution, they get soft credited....Read more
Batch entry of gifts (checks, cash, etc.) is a much requested "missing feature" in CiviCRM. Thanks to a generous sponsorship commitment from the Electronic Frontier Foundation, we are about to launch a Make-it-Happen campaign to implement this feature for the next release (4.2). We've spent some time discussing requirements with folks at EFF and several other organizations, and we've reviewed analogous functionality offered by several of the proprietary donor management products. The purpose of this post is to share the draft specifications for the feature and solicit feedback from others in the community.
The goal is to provide a streamlined interface for data entry of batches of contributions and membership payments. A simple batching concept will be introduced to provide verification of count and totals. The feature will use a grid-style input form with the columns controlled by a selected profile. This...Read more
There have been several hook() or Drupal module based solutions for "members only" pricing for events or for other 'discounts' related to memberships.
The whole concept of this code is that any 'member only' fee label must contain a specific word or phrase, in my example this word is "Member". Staff must be trained to do this - it is relatively simple to do so.
How it works:
1. Place this code in a block, selecting "full HTML" or "unfiltered" input type, and assign the block to an inconspicuous region in...Read more
Notice to non-developers: This post is about how some functionality in 4.2 will be implemented in code and in the database, with very minor changes to anything visible through a browser. If you're not a developer, it probably won't interest you.
Simplifying the Codebase
As part of the CiviAccounts project we are looking to redo some of the implementation of the configuration and processing of payments for contributions, memberships, and events. Currently the processing for each of these three types of objects has two paths: one for a simple configuration of the objects, and one using price sets. This means there is more code, more complexity, more possibility of errors, more work when making changes, and more need for testing.
As we refactor the existing code we're looking at keeping the simplified UI for configuration and administration, but implementing everything under the hood using price sets. Before going ahead with that, we wanted some...Read more