We’re almost 3 weeks into the release of version 4.6 and, based on today’s stats, it’s been downloaded from http://civicrm.org 1,839 times. We’d break 2,000 downloads easily if we added in those from SourceForge, however for the sake of this post, I’m interested only in those from the CiviCRM website because that’s where we’ve promoted a campaign to donate before downloading the latest version.
Blogs
Views, VBO and CiviCRM Entities modules provide an interface for bulk updating Civi data; updating Participant status for attendees 'at the door', entering 'end dates' for multiple Relationships, etc.
It’s been on my task list to post an update about the fundraising at CiviCRM, so I thought now would be a good time - with the release of 4.6 and a more concerted effort to encourage financial support - to review CiviCRM’s path to sustainability. The bottom line is that there's a significant and unsustainable gap between our revenue stream and our very modest operating expenses.
Have you ever wanted to start a local CiviCRM user group? Or introduce CiviCRM to more local nonprofits? NetSquared might be able to help you kickstart a meetup through a co-hosted event.
Still looking for a compelling reason to attend CiviCon Denver? Why not listen to past attendees and presenters to learn about what they took away from attending other meet-ups?
Estamos muy contentos de tener dos CiviCon el próximo 28 de Mayo en Europa, una en el Norte en Amsterdam y otra en el Sur en Madrid. Es una gran oportunidad para asistir a una conferencia regional donde conocer y aprender de la gente que hace posible CiviCRM.
We implemented CiviCRM in our non-profit company CEPS (www.ceps.eu) for it fits very well our needs. We use it almost out of the box for contact management, memberships, mailing and event registration.
We get a steady trickle of requests regarding changes to what receipts go out when someone signs up for a regular payment. We use an extension to help with this 'norecurreceipt'. The extension basically prevents the is_email_receipt from being set to ON on the civicrm_contribution_recur table - thus allowing the inital mail to go out but not the subsequent ones.