Blogs

This week we're releasing CiviCRM 3.1.6 and 3.2.beta5 - they are both regular bugfix releases, however, they also bring a fix to recently discovered security vulnerability, which in specific conditions allows an unauthorized person to access some CiviCRM functionality. Please make sure you upgrade your production installations running 3.1.5 and earlier to 3.1.6 to avoid the risk.

I have created 2 custom searches at that I find useful for finding upcoming birthdays and wedding anniversaries. Hopefully these are useful for other folks too.

The new searches can be downloaded from: http://wiki.civicrm.org/confluence/x/WgDvAQ

Here we are with the fourth BETA release of version 3.2 - it is now available for download. You can also try it out on our sandbox site. Please remember this is a BETA release and it should NOT be used on production sites, even though we're getting closer to stable.

This release includes several major new features/highlights:

Sendgrid is a relatively new cloud-based service that takes care of mailing list SMTP delivery and attempts to get the highest possible deliverability rate. We didn't want to have to manage our own SMTP server here at the Participatory Politics Foundation, so when we migrated to CiviCRM recently, we decided to take the sendgrid route for SMTP.

Following on from our training camps last summer, we are very pleased to announce another two training events in London this September/October. The first is aimed at users and administrators, and the second is aimed at integrators, implementors and developers.

We'll have folks from around CiviLand joining us for these trainings (Archduke Lobo, Grand High Wizard Dave Greenberg, and more) so you'll be learning from the experts.

Here we are with the third BETA release of version 3.2 - it is now available for download. You can also try it out on our sandbox site. Please remember this is a BETA release and it should NOT be used on production sites, even though we're getting closer to stable.

Important message for translators: beta3 is a string freeze release - which means, you can safely start your 3.2 translation work - not too many new strings and/or string changes should show up to mess with your work. For more details, please refer to previous release announcement.

Now following with information about 3.2beta3: this release includes several major new features/highlights:

UPDATE: Dec 17, 2010

dharmatech has contributed a similar module to drupal.

d.o. page: http://drupal.org/project/civievent_discount

civi blog: http://civicrm.org/blogs/dharmatech/add-coupons-events-module

great job dharmatech!

Last Friday I we had a BeNeLux CiviCRM meetup in Vianen, with 21 attendants from all three countries (Belgium, Netherlands and Luxemburg). Lobo was present too as he was in the neighborhood (Paris?) anyway.

It was a very inspiring sessions, that got off with a good introduction. We split up in different parallel sessions, where Lobo did a general introduction, Erik Brouwer did a session on localization and I discussed my showcase of synchronizing data between CiviCRM and an Oracle application at De Goede Woning.

Here we are with the second BETA release of version 3.2 - it is now available for download. You can also try it out on our sandbox site. Please remember this is a BETA release and it should NOT be used on production sites, even though we're getting closer to stable.

With 3.2beta2 we're introducing our new translation maintenance process. It's time to announce something we called "soft string freeze" - we reviewed and checked for formal correctness the strings that are extracted for translation. Now, we are giving ourselves and our community one week, until beta3, to review our user interface and see if we need any improvements and fixes before formal string freeze. Just as a reminder, after formal string freeze, we'll do our best to avoid changing any strings in CiviCRM user interface - this way, we won't be stepping in our translators' ways and breaking ongoing translations. "Soft string freeze" means it's a last moment to take a look at your string bundles, see what has changed since 3.1, see if there is no quirks and annoyances to be fixed - and report any problems (ideally, with patches) to be fixed before formal string freeze.