As we are getting ready to roll out the first alpha for CiviCRM v3.3, I figured a status update on some of the cool new features of 3.3 was in order. So without further ado, here are some of the cool new features that are part of 3.3
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.
October 15, 2010
By kurund Filed under CiviCRMAs a part of 3.3 release we will be deprecating all v1 api's and if you are still use them, it's a good time to migrate to v2 api's before upgrading to CiviCRM v3.3 release.
CiviCRM api v2 were introduced in v2.0. For every v1 api there is equivalent v2 api.
Reason for removing v1 api's:
October 13, 2010
By michaelmcandrew Filed under DocumentationA quick look the book CiviCRM a comprehensive guide: how we got here, and our plans for the future
We recently got fifty copies of CiviCRM: a comprehensive guide printed on demand for some training events in the UK. Being able to hand out a 300 page book as a supplement to the training went down really well with participants: holding something in your hands in a world which is predominantly online world is quite reassuring, it seems!
October 13, 2010
By Eileen Filed under CiviCRMJust a quick update to say that the 'de-dupe exception table' initiative is now funded for release 3.3. This will allow those poor souls struggling through a big de-dupe to mark some contacts as 'non-matches' and not have to wade through them every time.
This initiative was sponsored by
Creative Commons
Community Builders Australia Pty Ltd
Australian Greens
NES Alumni and Friends Nonprofit Partnership
October 5, 2010
By ErikHommel Filed under CiviCRM, SprintsToday is the last day of the Bristol code sprint, which was a great experience! Lots done, climbed the Cheddar Gorge and tasted Kurundś famous lamb.... I will also always remember it for finding out I was part of the API team :-)
On a serious level, it is a good idea to have a team of people that take care of the API's. And taking care I think involves:
October 5, 2010
By shot Filed under CiviCRM, SprintsOne of the goals of the (ongoing) Bristol code sprint was taking a stab at making the API calls properly permissioned, and I’m happy to report that after two days of very fruitful hacking with Erik and Xavier we’ve landed the crux of it on trunk (to be released as CiviCRM 3.3 later this autumn).
October 3, 2010
By michaelmcandrew Filed under Extensions, Finance and Accounting, SprintsToday at the Bristol Code sprint a few of us made a concerted effort on getting making Giftaid 'plug and play' for Civi.
Our starting point is code written by Millertech and our aim is to get it into a state that we can package it as a Drupal module. Once we've done that, we're hopeful that we'll be able to package it for Joomla also.
October 3, 2010
By ErikHommel Filed under CiviCRMA couple of blog entries back (http://civicrm.org/blogs/mbriney/contacts-erd-v31 to be precise) Matt Briney was kind enough to share the contacts ERD with us! I promised to put some more on. The entire CiviCRM ERD is too big and complex to be useful in this format, but I have just created one for the location point of view.
October 1, 2010
By xavier Filed under Architecture, Interface and design, TrainingHi all,
For the training in london, we wanted a simple example that illustrates how to customise and improve civicrm for specific usages using the ajax interface. I'm sharing the result with you, hoping you will find it useful.
One common workflow we have is to change the status of an activity from "scheduled" to "complete". The default way is to click on edit, go to the full form, change the status, save, and go back to the list of activities
We are going to improve it with a "one click click complete": on the list of activities, we transform the status column into an action (when "scheduled"), and when I click on it, it changes it to Completed, without changing screen. For that, we are using the ajax interface and the activity api. Copy the template templates/CRM/Activity/Selector/Activity.tpl into your override directory, and add a few lines of jQuery at the top:
{literal} <script> jQuery(function ($){ $("td.crm-activity-status_1") .attr("title","Change the status to completed") .css("cursor","pointer") .click (function () { aid=$(this).parent("tr").attr('id'); var activity_id = aid.replace("crm-activity_", ""); cj().crmAPI ('activity','update',{id:activity_id,status_id:2}, {callBack: function(result,settings){ if (result.is_error == 1) { $(settings.msgbox) .addClass('msgnok') .html(result.error_message); return false; } else { $('#crm-activity_'+activity_id) .removeClass('status-overdue') .find('td.crm-activity-status_1') .removeClass('crm-activity-status_1') .addClass('crm-activity-status_2') .html("Completed"); } } }); }); }); </script> {/literal} Oh, it's magic! What does it do in detail ? Well, you should attend a developer training, you will discover it, and way more ;) X+