Blogs

A member sends several separate payments to cover outstanding dues on a single purchase, like an expensive membership or a table at an event. How are you going to record this?

A conference participant selects “Pay Later” on several different event registrations, and later wants to pay them all in a single credit card transaction.  How are you going to support this?

Thanks to successful Make It Happen on consolidated cron jobs, we can set just one cron job per site.

As described in the docs, you can set this cron job using either an "URL" method or a "CLI" method.

Although the API changes in 4.1 are not as obvious as took place in 3.4/4.0 there have been quite a few changes under the hood. This is a fairly detailed explanation of what's going on inside the API wrapper.

<Cross posted from Advomatic.com The code blocks will be easier to read there.>

Sometimes after launching a new site our clients find that there are fields and features in CiviCRM that they don't use.  We are working with a client that wants to remove all fields and features that aren't useful in order to simplify their user interface and make it easier to use.  This includes things like SMS features, email signatures, and demographics.  There are also several fields that they wanted renamed to be more consistent with the legacy system that they migrated from.  To fulfill this requirement I used a combination of template overrides, and CiviCRM's translation system.  

First up I should point out that if you do want to go down this path you need to make clear to the client that this will take a fair amount of effort up front (hopefully less for you now that you are reading this recipe).  Additionally, if/when you upgrade CiviCRM these customizations will need to be reviewed at the very least, and possibly even re-done to some extent.  So while this customization will make things more usable for CiviCRM administrators, it will add cost to both the initial site build, and to ongoing maintenance.  

This feature has been sponsored by the New York State Senate. The issue spec is on the issue tracker.

I am very glad to have opportunity to work on this feature and sharing my thoughts and experience for same :) . This feature is added in trunk and scheduled for version 4.2 release

It has been an amazing Code Sprint in London this week. Lots done in the week, including GiftAid module fixes to work with Drupal 7/CiviCRM 4.x branch. CiviMobile, CiviCRM testing, Documentation.

Thanks for Katy for arranging the work space in CAN Mezzanine. Thanks to the members of the community who participated in the event and a big thanks to Lobo and Kurund from the core team for making the sprint a success.

Hi,

The code sprint in London has finished yesterday. It's always a pleasure to see old civi friends and meet new ones. Thanks to Michael and Katy to have organized it. Time for a quick update of what I've been working on with the most obscure title I could find. My focus has been on usuability to make civicrm easier and faster to use.

We're wrapping up the London code sprint today. We've done a decent amount of book review, which will stand us in good stead when we get to Woolman and we've also made some minor improvements to the books at book.civicrm.org.

Books now have a 'breadcrumb' which show you what section you are reading and they also have proper titles, which should make them more visible when people are googling for help.

The team is excited to announce the second stable release of version 4.1  - with support for Drupal 7, Drupal 6, Joomla 1.7/2.5, and Wordpress 3.3. You can download the release now from Sourceforge.

We're doing a fair amount of work on the book review at the London sprint. It would be cool to have others involved (remotely or in person).  If you want to help out then