Along with the Core Team, several contributors in the community have been testing Gitlab as an overall project management and communications tools for the CiviCRM community. Though it’s still a work in progress, we’re happy to start pushing it out to the broader community in hopes that it can provide a more cohesive platform for project management and community engagement.
How do we envision it working?
Last year, we introduced teams and working groups as a way to organize our work and attract new contributors to the project. With the addition of Gitlab, we’re reinforcing that structure while adopting an open (yeah, Gitlab is open source), transparent way to organize and manage all of the various initiatives undertaken by the CiviCRM community.
Currently, we’re organizing Gitlab into functional groups, specifically “Core...Read more
CiviCRM Entity Reference Field is a submodule of the CiviCRM Entity project. One of the many advantages of installing the CiviCRM Entity module is the ability to use Drupal’s Entity Reference module to reference CiviCRM data from nodes, terms, or other entity types. Many people are using the Inline Entity Form module, which provides field widgets that allow you to create, edit, or delete a referenced entity from the parent form.
If you reference CiviCRM contacts via an Entity Reference field and use Inline Entity Form, you’ll often want to include the ability for the user to create or edit subsidiary CiviCRM entity types, such as the email, phone, and address entities. This can get tricky with CiviCRM integration. A regular entity reference field stores a target entity id in a Drupal field table of the Drupal database. CiviCRM Addresses are stored in the CiviCRM database, and can be created by different types of users and in many different ways. In addition, Drupal and...Read more
As of CiviCRM Entity 2.0-beta4 the sub module called CiviCRM Entity Price Set Field provides a Drupal field type for the Event entity type. In this article we’ll review the features of this submodule and discuss how to configure and customize it to fit your needs.
Event Registration on the Event view page
When configured to display on the Event view pages, this field generates a registration form that supports:
- Registering multiple Participants
- Uses the event’s price set and all price fields of any type
- Pay later or credit card transactions utilizing CiviCRM’s payment processing
- Default values for the profile fields corresponding to the logged in user’s contact information ...
CiviCRM Entity 2.0-beta7 has been released.
Pick it up now at the Drupal.org Project Page
Changes since beta6:
Add Rules action Assign Contact to Group
Add Rules action Remove Contact from Group
Add Integration for IM entity
Add Integration for Website entity
Add integration for Contribution Recur
Add Rules event for CiviCRM Price Set Field 'After Successful CC Transaction'
CiviCRM Price Set Field , improved support for price fields with multiple checkboxes
Fix issues with CiviCRM Core Contribution Recur Views integration
Enable CiviCRM Entity Reference field on parent entity 'add', Inline Entity Form Single widget, for Contacts...
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
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
When email was first designed, security was not considered important and up until fairly recently it was still possible to send an email from any address and get away with it.
However, as spam, phishing and spoofing attacks by email have become increasingly common there have been various attempts to make email more secure. In the last year or so the major providers (AOL, Google, Microsoft etc.) have all seriously tightened their security and authentication requirements for validating and receiving email. The result of this is that a lot of legitimate email is now being classified as spam or rejected by those providers. In order to ensure that your email continues to be marked as legitimate and received by these larger providers it is now almost essential that you implement SPF, DKIM and DMARC on your domains otherwise many of your...Read more
Way back when, in the early days of CiviCRM, there were two CMS’s supported, Drupal and Joomla, and CiviCRM’s codebase was complicated, but ran reasonably well. After a few years, the code was greatly improved but also significantly expanded to include a tremendous amount of additional functionality, and thus CiviCRM became a serious server resource hog. Finding hosting that could run it at all was sometimes a challenge and finding a host that could run it well was difficult.
In those days, Drupal sites far outnumbered Joomla sites, both generally on the web and also for CiviCRM sites. Since CiviCRM released WordPress support, however, what we have seen at CiviHosting is an increase in WordPress sites and today in fact, for new installs, we see that more clients choose WordPress over Drupal (by a small percentage).
Back in the early days, the majority of CiviCRM users were small to medium sized organizations, but over...
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...