It's 19.50, I'm in the train from Brussels to home, on my way back from the CiviCRM developer camp. Erik Brouwer has just left the train, Eagles on the headphone and there's a multicolored display of non-identifiable ligths thru the window.....just another 90 minutes and I will be on the couch with a glass of red, cats purring on my lap and telling Floor all about the two days. So what was it like, this developer camp?
Cross-posted at The Nerdy Adventures of Wes.
CiviCRM isn't always the most predictable codebase. Recently I needed to get and set some custom field values in a hook I was writing. The hook's job was to calculate some custom field values and create some contact references when a contribution was created or updated. As always, dlobo was a huge help (he's the CiviCRM guru, find him in #civicrm on Freenode). Here's what I did to set a couple of custom fields in my _pre hook:
The Dutch housing corporation De Goede Woning did a prototype with CiviCRM in the last quearter of 2009. At the end of the prototype the project group wrote a recommendation to the Management Team:
- take the basic decision to start using CiviCRM as their CRM
- make a project plan to start using CiviCRM in the sales and customer service part of the organisation
- to develop links to/from their main transaction system and their document management system
Last Wednesday was a packed usergroup with more than 25 people squeezed into our meeting room in Scrutton Street. We were split more or less evenly between end users and developers/implementors, and between current and new users. There was a definite Drupal bias in the room, but there were some vocal Joomla implementors too. It was good to see familiar faces from last years developer camp and user training, as well as people that have started using CiviCRM in the past few months, and those that are just starting out.
v3.1 includes several COOL new features: