We've been using CiviCRM at Bay Area Children's Theatre since 2008, and started using it for ticket sales shortly thereafter. CiviEvent was really designed for event registrations, and there are some differences between an event registration and a ticket purchase, but we found that CiviEvent gave us enough flexibility to use it for ticket sales -- especially with price sets.
Blogs
Unfortunately we have discovered a syntax problem in the 4.2.3 upgrade script which will cause the upgrade to fail under certain circumstances. We are pulling this release and will replace it with 4.2.4 shortly.
If you've downloaded 4.2.3 and not tried the upgrade yet, you can trash that tarball and then download 4.2.4 shortly.
If you tried to upgrade using 4.2.3 and got the fatal error, you can safely download and run 4.2.4 shortly.
This issue will not affect your site if you installed a new CiviCRM site using 4.2.3.
A quick recap of recent CiviSprints in Europe.
Training courses, youth groups, sports classes, drama clubs… events like this form the bedrock of many non-profit organisations. As CiviCRM can’t yet handle such complex ‘recurring’ events, a new Make It Happen campaign aims to change that.
WordPress is the most popular content management systems in the world and CiviCRM is the most popular open source CRM for non-profits and the civic sector. With CiviCRM 4.1 support for Wordpress, Wordpress users were able to use the most powerful CMS + CRM combination ever.
Hello There,
I'm pleased to announce the CiviMember Role Sync Plugin for WordPress is available now.
Hello folks. I am super pleased to say that starting from January 2013 I'm going to have the pleasure of serving for six months as CiviCRM's 'community manager'.
So what is a community manager?
To my mind (though actually, I am using a significant part of Jono Bacon's mind as well here) the following things are key to this role:
The team is excited to announce the third release of 4.2 stable with support for Drupal 7, Joomla 2.5 and WordPress 3.3.
At the Apeldoorn sprint today we had several discussions about street parsing and what we should do about it. A couple of solutions came up, I spoke first with Joe Murray and Xavier Dutoit. At that point in time using Extensions per street parsing seemed a logical solution. Discussing a little more with Lobo and Tim Otten the idea changed, and perhaps one Extension for international street parsing should be enough.