Blogues

The attached chart came out of a discussion between Kasia Wakarecy, Lola Slade and myself (Lynna Landstreet), at Freeform Solutions, about some issues we'd encountered when trying to to do major version upgrades of CiviCRM and Drupal on a client's site at the same time. Since we're likely to have a number of other combined upgrades like that to do in the future, we wanted to iron out the best process for doing them as smoothly as possible.

It's here! The much anticipated new CiviCRM 4.3 is ready for prime-time. Congratulations to everyone in the CiviCRM community who made this happen.

Here are just a few of the exciting improvements in CiviCRM 4.3.

During the last few hours of the Civi Sprint in London, Jen (who is new to Civi) and I had a look at some basics on the CiviCRM website (civicrm.org) and have identified some problems and possible solutions.  Noting too radical mind and most involve minimal changes to the actual content as that's perhaps for a later date.

The team is excited to announce the ninth release of 4.2 stable with support for Drupal 7, Joomla 2.5 and WordPress 3.3.

We are currently shortlisting Make it Happen campaigns for the 4.4 release.  For those not familiar with Make it Happen (MIH), it is a way to crowd source the functionality you'd like to see in CiviCRM. We want to have a finalised list of MIH ready for people to contribute to online by April 14th. If you have been thinking about an MIH for a while, now is the time to submit it for the 4.4 release.

Proper GRM tools can make all the difference in the success or failure of your herd. As many developers have found, working with a proprietary goat resource management system can seem simple in the beginning, but customizing it to your herd's specific needs can feel like eating brambles. With the new CiviCRM extensions framework and easily digestible API 3.0, developers can dig in and produce at an unprecedented rate.

Announcing the final beta release of 4.3 for Drupal 6-7, Joomla 2.5.x and WordPress. Time to really put it through it's paces - we recommend upgrading a copy of your database and trying out all the usual (and unusual) things you normally do with your CRM to see how much better 4.3 makes your life (and hopefully that everything works as expected).

The decision was made some time ago. We are going to migrate our organisation's administration to CiviCRM, on top of Drupal. We needed some training, so we contacted Mediaraven. I'm not sure what exactly happened then, but some days later we were suddenly registered for the Benelux developer and implementer training. A two day training in Ghent, at the Mediaraven headquarters. With about 20 civicrm-enthousiasts from the Benelux and beyond.

CiviCRM has the ability to automatically grant memberships to related contacts. So, for example, when a company purchases a membership, employees of this company can be automatically extended the same membership. In the user interface, these memberships are then flagged as ‘by relationship’.

But up to today this was an all-or-nothing proposition: all employees of the company where automatically granted a membership, with no ability to neither limit the number of related memberships, nor choose which of the employees would get these.

We're fortunate to find Sir Civi in the midst of the Bug Smithing Weekend, and get a quick interview from him while his horse is being watered. So how's it going ?

Sir Civi: "Twenty two. So far, that is. Nasty creatures, them Bugs. Spoil the fun for everyone. Lurking in a piece of code that noone tested, popping up at the least opportune moment (like when you're doing a demo). Takes the fun out of moving to the next release."