Blogs

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."

Announcing the fourth beta release of 4.3 for Drupal 6-7, Joomla 2.5.x and WordPress. In the spirit of community participation this release kicks off the start of the final push: Ye BugSmithing Weekend goes from now until Monday, when we'll announce the grand prize winner!

We want to propose a Make It Happen for a CiviCase configuration UI (see forum post http://forum.civicrm.org/index.php/topic,25791.15.html).

Lisa presented this work at the SF Meetup in March. Her presentation slides are here

Three years ago I set up a Drupal-based community site for our children’s K-8 public charter school. As the school’s needs grew, I integrated CiviCRM to enable online enrollment, tour registration, ticket sales, volunteer hour tracking, and other functionality that had previously been accomplished through unwieldy paper forms.

As I began to work more closely with a local arts education non-profit, I realized the lessons I had learned from working on the school site were directly applicable to the organization’s needs. SFArtsED runs a summer camp program for children. Till this year, all registrations were completed  on a paper form that was sent, along with a check, via snail mail. The Registrar mailed back four forms to the parent, who filled them out and mailed them back to SFArtsEd, along with a receipt for payment. Last month I set out modernize their camp enrollment process using Drupal, CiviCRM, Ubercart and Webform Integration.

After my previous blog post, i have been working on making progress on working model w.r.t NoSQL and config. Starting with civicrm cache was a good idea. Keeping in mind NoSQL, new config system and what Eileen has already done with settings, here is what i planned and accomplished  :

When you think of it, it's quite amazing : open source communities bring out the best in people. Like all of you who participated in the first Bug Smithing Day, and ran 4.3 beta through a series of real-life tests, upgrades and API scripts. Even if you didn't find a bug, thou art truly thanked for thy effort.