CiviCRM Entity is a contributed module for tightly integrating and extending CiviCRM with Drupal. This module exposes CiviCRM API entities as proper Drupal entity types. This is HUGE as it allows you to make CiviCRM data available within your favorite Drupal tools such as Rules, Views, and EntityReference. I’d like to present another advantage of Drupal entity types, and that is Drupal fields.
By enabling CiviCRM Entity, you can add Drupal fields and associate with CiviCRM entity types such as Contacts and Events. In fact, any of the hundreds of Drupal field types can be used with CiviCRM Entity. You may be asking yourself, “Shouldn’t I use a CiviCRM custom field? Why would you want to use Drupal fields?” The correct answer is, you should choose the right tool for the job.
CiviCRM is great at having the business logic and infrastructure to support event registrations. CiviCRM has price sets, price fields,...Read more
Before I started working as a CiviCRM consultant, I was a CiviCRM user at a small nonprofit. We got a large chunk of our revenue through grassroots donations, but we never had an opportunity to see how we compared to other organizations like ours.
(TL;DR – you should install the Individual Donor Benchmark Survey extension, run the report, and submit your survey response.)
Nowadays, some proprietary donor databases collect users’ data and publish reports, but besides being creepy, they can’t get good data without involving organizations directly. They also only cover users of a single software system.
Besides, how do you know the data covers organizations like yours?
The Individual Donor Benchmark Survey was developed by Third Space Studio to address these...Read more
Some of you will know, use and might even love the CiviRules extension. We certainly do! Quite a few of the organizations we support with their CiviCRM stuff use and love it, and judging by the question on StackExchange and issues and pull requests on GitHub quite a few more do too!
This is wonderful! But it also means that quite a few organizations are faced with the challenge of keeping CiviRules up to date with the latest CiviCRM versions. And want to make sure the functionality remains the same whenever new upgrades or little fixes to CiviCRM happen. So we think it would be nice if we were able to:
- ensure CiviRules is compatible with the latest and greatest core CiviCRM
- add a bunch of automated unit tests to CiviRules that would be run together with the core automated tests so we immediately know about bugs or software conflicts when something changes in core.
To make this possible we need funding. Initially some funding to make...Read more
The CiviCRM extensions community is thriving. Presently there are 270 extensions listed in the Extensions Directory and countless more scattered around the Internet in GitHub repos and the like. Last year, 35 extensions were submitted for review in 2016, a 400% increase from 2015!
Unfortunately, only about 50 extensions are available for one-click installation within CiviCRM. The sharing of code is central to the ethos of our community, but our ability to reap the benefits of collaboration depends on our ability to communicate about our efforts. Increasing the number of extensions available for in-app installation will lead to:
- increased attractiveness of CiviCRM as a platform, since new functionality is just a click away (à la Wordpress); and
- less duplication of effort (last year I developed an extension that largely duplicated another partner's work because I didn't know their extension...
My clients regularly need to import data from sources such as Just Giving, CAF, and various other sources like Mailchimp downloads. The problem they had was that the data was a mix of contact and contributions, and some of the rows belonged to new contacts, others belonged to existing contacts. Sometimes they had a scrappy list of names and emails where the name was all in one field instead of split out. You know the sort of thing.
At the time (a few years ago) I knocked together a Drupal module to help pre-process this data so that it could be used efficiently with CiviCRM's built in import functions. I made it in Drupal because that was quickest for me to develop a solution and they used Drupal, but I've now re-written it as a native CiviCRM extension that should work for Drupal users, and the ever proud and cheerful (but wrong) Wordpress fans alike. Maybe even Joomla. ;-)
How does it help me?
It takes your spreadsheet (...Read more
JMA Consulting is pleased to welcome Jon Goldberg as our new Director of Operations effective today.
After a brief stint as a political organizer, Jon spent 13 years working in various capacities at a non-profit legal organization, primarily in IT. In 2010 he co-founded Palante Technology Cooperative and started their CiviCRM department, where he worked for 7 years. Outside of work, Jon can be found engaging in queer community organizing, (dis-)assembling electronics, and training parrots.
"I'm really excited to have Jon join us given his keen appreciation of how to help progressive organizations achieve their missions using CiviCRM. He's got a deep and wide knowledge of CiviCRM. I appreciate how he gives back to the community like through StackExchange, where he is the top ranked CiviCRM contributor," said Joe Murray, President of JMA Consulting and co-author of...Read more
cv (https://github.com/civicrm/cv) and
civix (https://github.com/totten/civix) are Unix/CLI tools for developers.
cv provides access to your Civi site on the command line, and
civix generates skeletal code for new extensions. We've had a few recent updates to each of these tools, so I wanted to introduce
cv more formally and then recap some of recent improvements for each tool.
cv originated as part of the Testapalooza project which broadened support for automated tests in CiviCRM -- testing of CiviCRM extensions or external integration modules; testing with PHPUnit or Behat or Codeception; testing for headless scenarios or end-to-end scenarios; ad nauseum. In all of these cases, we start with some...
- End users...
This little story about financial transactions has a couple of objectives:
1. share what we want to do for the benefit of each and everyone
2. find out if there are more organisations out there that would be interested
3. even better, organisations out there that want to co-fund and influence!
At the moment CiviCRM allows for the linking of a financial account to the financial type as a basis for data exporting to whatever software you are using for accounting. You can also attach an asset type financial account to a payment instrument. When creating, updating, cancelling or refunding a contribution the financial 'traffic' between the configured financial accounts is nicely recorded in the financial transactions table. We are not sure...Read more
Ginkgo Street Labs is pleased to announce the availability of CiviVolunteer 2.2.
Two themes are evident in this release: improving stability and furthering the multi-tier use case. The increased adoption of CiviVolunteer as a multi-tier system, where one organization facilitates the volunteer programs of partner organizations, has necessitated improvements to permissions granularity as well as streamlining of interfaces. Improvements in CiviVolunteer 2.2 include:
- Version 2.1 introduced settings for volunteer project defaults under Volunteers > Configure Volunteer Settings. Version 2.2 builds on this work, adding the ability to set defaults for a project's manager, beneficiary, and other relationships.
- New permissions Edit Volunteer Project Relationships and Edit Volunteer Registration Profiles provide an easy way for site administrators to simplify the volunteer project creation workflow for partner organizations or...