CiviCRM 3.0.alpha2 released

We’re happy to announce that CiviCRM 3.0.alpha2 is now available for download. You can also try it out on our sandbox site. Please remember it’s an alpha release and it shouldn’t be used on production sites. Check out the blog entry on the previous alpha1 release for a run-down of what’s new in CiviCRM 3.0, and this list for issues that were fixed since 3.0.alpha1. A full list of changes, improvements and bug fixes in this release is also available on the wiki and in the issue tracker.

Invoices 3.0 & beyond

I wasn't really sure when I wrote my first blog on accounts and CiviCRM whether it was a topic that would draw much interest but in fact I got a lot of really thoughtful comments and something of a blogathon took place. I have some ambition to write another piece summing up what I think has come out of the discussion - but in the meantime I want to pick up now on something Dave & I have talked about a little bit on the forums: invoice numbers.

Perl client module for CiviCRM REST API

I just uploaded the first version of the Perl client module for the CiviCRM REST API. You can download it from CPAN here. This means you can now create, edit, delete, and retrieve (most of) your CiviCRM data from Perl scripts and programs. I'm using it to provide integration between the Perl CMS WebGUI and CiviCRM. But you can use it for many different things; it's very general purpose.

Report back from NYC CiviCRM Meetup - Aug 6, 2009

- Here's a report back from Sacha Stanton

The New York Meetup was a great success last night, as 33 people got a glimpse into upcoming releases, several case studies, and great open floor discussions. Dave Greenberg, core contributor, joined in via Skype video to provide insight into upcoming features and answering questions.

Report from the latest San Francisco User Meetup

The second SF Bay Area User Meetup was hosted last night by Wikia and Wikimedia Foundation folks (big claps). We had an excellent turnout (the room was packed) - with a nice mix of backgrounds ranging from prospective users to experienced folks and a few developers. The first part of the meeting featured 3 presentations:

Introducing the alpha release of CiviCRM v3.0!

The day has come! We are excited to announce that our 3.0 ALPHA release is now available for download. You can also try it out on our sandbox site. Please remember it's an ALPHA release and it shouldn't be used on production sites.

This release introduces many new features, some of them really important, that's why we decided to start a new major number series in CiviCRM versioning. One of the most important new features is CiviReport, which is a completely new component for advanced reporting on your constituent data. Second significant change is a major user interface redesign with a goal of increasing usability. CiviEvent was also improved with waitlist functionality, pending status expirations, and an option for administrator approval for participants. A full list of changes, improvements and bug fixes in this release is available on the wiki and in the issue tracker.

Scoping out basic CiviAccounts/CiviBanking

This post started out as a reply to Eileen's "Banking Screen?" comment on my previous post on this topic, but by the time I was done, I thought that this warranted its own post. I think that the core "Accounts" or "Banking" functionality that could be helpful to Civi users without getting too out of control, is:

CiviCRM 2.2.8 - Security Release

The team has released version 2.2.8 today. This release includes an important security update for sites which use CiviCRM Profiles to collect and / or share contact data. We recommend that all sites install this upgrade as soon as possible. Details here: 2.2.8 also includes fixes for IE8 compatibility, some improvements in Views2 integration and approximately 30 other minor bug fixes. You can review a complete list of 2.2.8 changes on the issue tracker. Note that the IE8 fix causes the browser to run in IE7 compatibility mode for all CiviCRM pages.

Is there a need for CiviAccounts?

We are finding that CiviCRM/accounts issues are becoming increasingly important for our clients, and Eileen's recent blogs and the discussion they are generating are a fantastic step towards helping find the best way for Civi to deal with financial transactions.

For example, I think it could be useful for Civi to ultimately develop functionality for maintaining simple bank accounts within CiviCRM, so that small organisations can maintain basic accounts without the headaches of integration with an external package.