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.
Do you need to allow parents to register their children? Tired of using custom data fields on a child to collect information about their parents and emergency contacts? Would you like the information collected during the registration to create (or update) the various contact records needed in the back-office? Then this blog post is for you. This recipe creates a contact record for each child, each parent, each emergency contact, the household contact, and also builds the appropriate relationships between each contact.
There has been some discussion in my organisation around possibly streamling the process and improvement process in regards to CiviEvents and Inviting people to come to the event.
The senario is this, We have end users who create events such as come to our Phonebanking evening. Yet there is no way through the event create / configuration process to then create an invite email or similar that could go to a target group. Say there is a group already created of people who have expressed an interest in phone banking.
I have just published an extension we (CiviCooP) developed for Coordinatie Vluchtelingen Vrijwilligers Ede (CVVE) CVVE is facilitating the organisation of activities for refugees in Ede. Many activities are organised by willing citizens and CVVE is the bridge between those citizens and the refuees. So to keep track of everything which is going CVVE needed an export of the events in their Google Calendar.
Last week was a busy one for the CiviEvent Widget plugin for WordPress. Not only did it cross the 2,000 download threshold, but new features were added to help you display upcoming events in a flexible way.
Read more for a summary of what's been added.
Per Dave Greenberg's suggestion, soliciting suggestions on state changes/plan to complete this MIH (parts 2 & 3 here: http://wiki.civicrm.org/confluence/display/CRM/Self+service+view%2C+update+and+cancel+for+CiviEvent+and+improvements+to+event+badges?focusedCommentId=268271620#comment-268271620)
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.
I am Tahir Ramzan, pursuing Masters in Computer Science at Virtual University of Pakistan. I am working on refunds, partial refunds and partial payments development for CiviCRM. Parvez Saleh and Joe Murray are mentoring this project.
Refunds and Partial Refunds:
Often, we need to tackle situation where one needs to make partial or full refunds. After this project users will be able to make refunds with friendly user interface and proper database records.
Views, VBO and CiviCRM Entities modules provide an interface for bulk updating Civi data; updating Participant status for attendees 'at the door', entering 'end dates' for multiple Relationships, etc.