As we focus on usability improvements for the 2.3 release, we are looking at ways to use screen space more efficiently AND ways to streamline commonly used workflows. With these goals in mind, we'd like folks to take a look at two newly implemented features in the 2.3 sandbox - a new shortcuts dropdown menu, and a streamlined workflow for entering offline contributions.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
A Make It Happen to move this into core for CiviCRM is currently running for v4.1. You can help make it happen by contributing here
Discounting events has been requested on the forums a few times. It also popped up both on IRC yesterday and was also needed on civicrm.org for our upcoming UK Training Camp. We decided to see if we could implement this via hooks and minimal / no changes to the core code. Turned out we can implement this this feature using three civicrm hooks and a helper fuction. We improved the core a wee bit by allowing the buildForm hook to inform the tpl system of any form elements added. The tpl then places these form elements at the top of the form. An event can have zero or more coupons. Coupons for an event are stored in the option group / value table. Each coupon code is a string (chosen by admin) and can be used a certain number of times. Coupons can also be used forever. A valid coupon gives the user a percentage discount on the event. Giving the coupon a 100% value basically gives the user a free registration. Coupons can be sent in via the URL or can be entered into the registration form.
Earlier this week we received some pretty excellent feedback from some CiviCRM users. This made our week, so we decided to share :). Erik Möller from Wikimedia Foundation writes:
CiviCRM definitely is becoming the leading open source product in this
space, and its growing mindshare and modular framework is helping it
to support other non-profit needs as well. Wikimedia has been using
CiviCRM as a fundraising backend for more than a year now after some
I took some photos at the recent CiviCRM Developer Camp in San Francisco. I have (finally) posted them online here: http://gallery.me.com/cap10morgan#100060
If anyone else has photos, feel free to upload them to that gallery.
One of the common needs of a contribution or event registration system is to track what campaign that transaction is destined from and what link originated the transaction. This allows organizations to calculate what links / web sites / advertising / mailings are most effective and use that information to influence their current or future campaigns. Some organizations (e.g. wikimedia foundation) use a three level tracking scheme: Campaign, Appeal and Fund, while other organizations might choose to use only one tracking field.
Lunch time of day two stands out as a high point of the book sprint. We'd spent the first day working relatively independently - brain-dumping the chapters about areas of CiviCRM that we knew the best and by Tuesday, it was clear the chapters making up our introductory section needed a re-think.
Last week I had the privilege of joining 10 other CiviCRM enthusiasts, along with a facilitator (Adam Hyde from FLOSS Manuals) for the CiviCRM Book Sprint. It was a fantastic experience on many different levels. More than anything else, it was great to meet in person and interact face-to-face with members of the core team and active members in the community—many of whom I’ve had forum-based contact with for several years.
The team has released version 2.2.3 with approximately 84 bug fixes and improvements. Notable fixes and improvements include:
The current way to track Households (HH) in CiviCRM is not easy. Over the last few weeks DharmaTech has been brainstorming how to better manage HH's and we had a chance at the CiviCRM developer camp to bounce ideas off of the core team as well as other developers in the community which was really helpful. What follows are our ideas to start the discussion.
With CiviCRM 2.2.3 and a patch to the Drupal Date API CiviCRM will be adding integration with one more Drupal Module, Calendar. This means you will be able to display CiviCRM events in Drupal calendars and decide what events are displayed by using Views filters in the same manner as you would any View.
