There is a new release here http://sourceforge.net/projects/civicrm/files/civicrm-stable/4.2.18/ - it deals with a regression on contact images introduced in a security patch. If you are having trouble viewing contact images you should upgrade to it.
Once upon a time there was a charity who was a visitor to both the lands of Xero and CiviCRM. This charity liked Xero and wanted contributions created in CiviCRM to be sent to the land of Xero. In the land of Xero these contributions would be called invoices and they would be matched with payments. Upon their return to CiviCRM all would know about their paid status and events would be confirmed and emails would go out and all would be be well.
LTS release 4.2.16 is now on sourceforge. Unfortunately there is an error on some admin pages in 4.2.15 which happened because the porting of the security patch was rushed. Hopefully this won't occur in future. Note the job.create api has also been added to the LTS (this is extra code only - no existing code was altered to port this)
As many of you know Drupal South is on next week in Wellywood. We don't have a big community down under but we are certainly keen to make you feel welcome in NZ
We will be running BOFs over the weekend & catching up for dinner on the Thursday night.
https://civicrm.org/civicrm/event/register?reset=1&id=419
If you are still around on the Monday & Tuesday we might look at a mini sprint. Drop us a line & say hello!
The community of developers and implementers is proud to announce the 4.2.10 LTS release of CiviCRM. LTS stands for "long term support" and the purpose of this release is three fold:
1. To provide bug and security fixes to those who are not ready to upgrade to CiviCRM 4.3 just yet
In New Zealand workplaces it's common to see a sign in the smoko* room saying "Your mother doesn't live here - do your own dishes".
People tend to follow this instruction as longs as:
a) there is not already a pile of dirty dishes next to the sink
b) and they can see where to wash the dishes, and where to put them afterwards.
c) their colleagues aren't setting a bad example.
I've recently been exploring creating CiviCRM entities as Drupal entities - using the drupal Entity API. I think so far I have only just touched the surface of the possibilities for this integration but I thought I'd post what I think some of them might be
I seem to spend a large amount of time helping people to get data back out of CiviCRM. I'm a big fan of the reports framework and up until 4.2 I made a number of improvements to the core reports for my customers. However, from 4.2 I switched to doing reports in an extension. I have been doing almost all my reports in the extended reports extension and have been playing with a few ideas in that extension. Some of them are well developed, others are in the early stages.
