Thanks to tremendous support from the CiviCRM community, development of CiviVolunteer 2.0 is well underway, with a beta slated to be released in time for the CiviCRM User Summit in September. Read on for a preview of what CiviVolunteer 2.0 will add to your volunteer management practice.
At the heart of any volunteer program is recruitment. CiviVolunteer 2.0 makes it easy for people to identify volunteer opportunities that fit their skills and interests. Signing up is easier than ever.
Searchable List of Volunteer Opportunities
Though CiviVolunteer allows organizations to recruit volunteers for a myriad of projects, it doesn’t offer a central listing of all the available opportunities. CiviVolunteer 2.0 changes that. Volunteers are empowered to choose the opportunities that most interest them. To start...Read more
I have just completed the first cookbook on CiviRules, with 2 basic examples and an example on how to automatically classify donors based on their contributing behaviour. Have a look, any comment is highly appreciated :-)
The CiviRules extension is in the CiviCRM extension list (https://civicrm.org/extensions/civirules) and on GitHub (https://github.com/CiviCooP/org.civicoop.civirules)
The Australian Greens developed 2 new custom searches to enable us to do data clean-up and to monitor for spam records that were coming into our system, mainly through the Drupal user registration form.
The first search (addresses needing fixing) has a number of different combinations to find different issues with addresses. This allows to check for where there is a state set but that doesn't match the set country or where the postcode isn't correct for Australian postcodes. All Australian Postcodes are numerical and are 3 or 4 digits in length.
This search also has options to check to check on addresses which we have put in "NCA" in the street address field, (this stands for No Current Address as there was no easy way to have addresses on hold).This is done so we can review and see if we have a more up to date address being added to the system.
We also have an option to check on and make sure that the city (we call suburb) field is filed out if state and...Read more
IATS has been a payment processor extension with CiviCRM for quite a while and has been actively developed & supported. If you are using the IATS extension you can say a quiet thank you to Alan, Karin & Stephen & stop reading.
If, however, you have been using IATS since the dark days before it was an extension and never switched over then it's time to make that change to ensure your site stays secure. Use IATS & need to check? Go to administer -> customise data & screens -> manage extensions and look for IATS. If it says installed - refer to the quiet thank you above (or better yet make a quiet donation to CiviCRM :-).
If not it's time to install the IATS extension https://civicrm.org/extensions/iats-payments - Alan has generously offered to provide support anyone making the transition. You can log an issue on the github repo if you need help -...Read more
During the past year, I've been working with a number of medium and larger organizations using CiviCRM, and have found a few gaps in CiviCRM's CiviContribute functionality, particularly around the management of recurring donors, which are often a really important part of a larger organizations' donor base.
To this end, I'm happy to share a couple of extensions that I've been developing to fill these holes, detailed below.
Feedback and patches welcome, as usual.
Also a side note -- if you're using our iATS Payments extension, we've just released a new 1.4.0 release, which is CiviCRM 4.6.x compatible.
Until I put together an official release, use this page: https://github.com/adixon/ca.civicrm.contributionrecur which...Read more
At the code sprint after CiviCon Denver, Tyrell Cook and I tackled some much-needed updates to Civi's wysiwyg system. A wysiwyg editor (what you see is what you get) is the mini word processor you use to compose emails, activities, notes, and other rich-text in CiviCRM forms. The old integration was written back in the days when CiviCRM wasn't so flexible (before extensions, or core resources) and aside from letting you pick between two editors, offered no other configuration options (e.g. to decide what buttons would be in the editor's toolbar). Plenty of room for improvement there, here's what we accomplished:
CKEditor is the most popular wysiwyg for...Read more
Message from Steinar (MAF Norge)
CiviRules is live and doing effective automation!
Two weeks ago, Wednesday June 10th, MAF Norway started to use CiviRules on their live production site.
We did set up one single rule, which starting from that day, saves us for approximately 1 hour work pr. day. That is almost 15% of one persons workload throughout the year!
The extension is open for download from github. It has some basics features and some cool stuff already.
If you also download the SMS API (or EMAIL API or PDF API), you could already schedule things like this:
- Automatically send a sms with congratulation every time a contact has birthday.
- Automatically put contacts in a certain group if they contribute over a certain amount.
- Automatically tag contacts that have changed their email adress.
This could again be combined with a report on some back office staff member....Read more
At the BHA we use a lot of Google Group mailing lists, and of course we manage all our contacts through Civi. This meant plenty of duplication - when the head of a particular section changed, say, we'd have to update it in Civi and then the Google Group. So we asked Veda Consulting to write us an extension that automatically synced the two. The first version is now out and available here:
- Syncs the contacts from multiple Civi groups (regular or smart) to specified Google Groups
- Adds a scheduled job to automatically sync once per day
- Adds contacts to the Google Groups silently - people don't get authorisation requests
- Supports multiple domains within a Google Apps system ...
Amnesty International Flanders (AIVL) have been using CiviCRM for a couple of years now, initially with memberships mainly but lately more and more as a fundraising tool. They have implemented CiviBanking for their incoming bank transactions and are now in the process of testing CiviSepa for their direct debits. We (as CiviCooP) are part of their CiviCRM family and work together with them to support their processes in the best way we can, making the most of CiviCRM. Other CiviCRM community members like Xavier Dutoit and Björn Endres (of Systopia Organisationsberatung) also for part of the team with some projects and ongoing development.
AIVL has an ambitious goal for their street recruitment, striving to increase the numbers of donors but also the retention rate and the donated amounts. One of the key development areas in this respect is the...Read more
This extension facilitates the ability to register different participant roles for an event in CiviCRM. At the moment CiviCRM will default the role used during online registration to the role chosen when setting up the event. So all the participants from online event registration would have same participant role. The work around for achieving multiple participant roles registered for an event would be to do an offline registration for a person and then select the respective role while doing so or on Drupal installations to use Webform.
How is this extension useful?
This extension provides you with a list of participant roles and their event registrations URLs. You could simply copy and send the URL to the desired participants.
Consider an example here:
You have an event called - Spring Summit 2015
Event Type - Conference
Guest Role - Attendee