The team has released version 2.2.1 with approximately 30 bug fixes and improvements. Notable improvements include:
Events: Provide a Drupal block which lists upcoming events
Mailings: allow users to cancel a running mail job
Contributions: re-introduce summary contribution information in search results
Pledges: support pay-later mode for pledge payments
You can review a complete list of 2.2.1 changes on the issue tracker.
Blogs
Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide. Subscribe to our newsletter to receive regular updates by email. We also have an RSS feed.
In brief: CiviCRM is having a good time here in Italy, associations and NGOs are very interested into the platform and how they may use it in order to reduce expenses and improve their "performance" in fund-raising tasks and management of databases.
We’ve just finished describing some of the new CiviEvent features we’d like to put in CiviCRM 2.3, including waitlisting and optional admin approval of participants. Please take a look at the CiviEvent - New Features for 2.3 wiki page and voice your opinions.
A quick braindump:
Profile are a great way of simplifying the interface and provide more focussed forms, but some of the goodies of the normal edit form are gone. For instance, the employer isn't anymore an autocomplete field. luckily, with the REST interface and a jquery autocomplete plugin, that's a few lines to add to make it work:
add on the templates/CRM/Profile/Form/Edit.tpl
{if $session->get('userID') > 0} {literal} jQuery(document).ready(function($) {
There are many places in CiviCRM where lists of records are presented... when you search for contacts, you get a list of contact records; when you go to manage events, you get a list of events; etc.
Kurund blogged recently about prototypes for improving usability for these record listings (we call them "selectors" internally)... and we got a lot of good feedback from that post.
Kurund and Amit on our team have now put up another iteration - which we'd love to have folks look at and comment on:
» Contact Listing
The past week was quite interesting and generated a fair amount of traffic and news about CiviCRM. It compelled me to summarize and link to the various blog posts :)
I think that here in the UK, we're missing out on something. Ideally I would like to have a central place to communicate and support each other with civicrm. Hopefully this will help organise meet ups and other events in the same timezone.
I have set up a provisional group at http://tech.groups.yahoo.com/group/civicrmuk/ if you could join up and start the ball rolling.
I'm putting this together to help the next version of civicrm. We needed a waiting list for events once they are full. Our needs will perhaps differ from a generic version but you have to start somewhere.
We started by detecting the state of the event with eventFull(). If it's full and the user is not already a participant OR in the waitinglist table, we give them a simple link which will add them to the waitinglist table.
After more than 5 months of design, development and QA - the team is thrilled to announce the release of CiviCRM 2.2 Stable. You can download the release AND / OR try it out on our public demo site.
2.2 features a number of exciting new features, including...
Personal Campaign Pages - add donors and constituents to your fundraising team
Soft Credits for contributions
CiviCase - Case management for human service providers (with thanks to Physician Health Program - British Columbia)
Simplified configuration option for CiviMail
Allow multiple custom field values for a given contact (e.g. "List the schools you attended, degrees earned and graduation dates")
Powerful new hooks for integrators and developers who need to extend and customize existing features
.... and 400+ additional improvements and bug fixes
You can find Release Highlights here.
A big round of applause is due to all the folks who downloaded, tested and submitted bug reports during the 2.2 release cycle. The alpha and beta packages were downloaded more than 4,000 times . Several hundred bugs and "improvements" were reported by community members and fixed by the team during the release cycle.
