Blogs

Good documentation is mission critical for the success of any software project. As a project we essentially have three audiences for our documentation:

We have a couple of customers who have been asking to be able to set-up recurring contributions against pledges. This seems to be a possibly contentious improvement so I'm looking for feedback on it.

As part of my final year studying Computer Science at uni I'm required to take on a 400 hour project. I've been wanting to create a mobile app for a while now and given that CiviCRM is lacking such a feature I thought it would be a good idea to embark on developing one. Hopefully the end result will be good enough to incorporate into core!

As of the Bourne, UK sprints last August, bin/cli.php has been completely re-written for 4.1.

If you are an integrator or user, you might not have noticed this file. It used to be a PHP class that was used by many of the individual scripts in the bin directory.

Now, it's a command line program designed to be run directly.

With cli.php you can run any function defined in the API version 3.

If you run the script without any arguments, you'll get a usage statement explaining how it works:

Background Pogstone's client had already been using a web-based membership database, however that system did not have any features related to households and other features needed when interacting with families and children. They also needed many features related to needs of a typical synagogue that were missing from the previous system.

Roll-out process

Last spring I started working on a Drupal module that would keep CiviCRM contacts in sync with Salsa contacts. I did a lot of the work on it and then, upon joining PTP's staff, the project unfortunately fell to the bottom of my stack.

The code is available...

git clone git://git.mayfirst.org/ptp/civicrm_salsa

... but it's barely code-complete and has had absolutely no testing, so we're not releasing it yet.

Recently we spent some time cleaning up the code base for Drupal's Views module in CiviCRM. This will be reflected in the 4.1 release of CiviCRM, at this point this was all written for Drupal 7, though should be portable to Drupal 6. There were a couple new features thrown in but much of this will focus on making the code base a little more efficient and easier to read.

The two major tasks were:

Four of the fr_CA translators team met in Montreal yesterday to discuss how to communicate, prioritize and exchange tips and tricks on how to translate CiviCRM.

We would also like to get in contact with other translation teams to know how they work. Here are some topics we discussed:

Important: This release includes critical fixes to resolve conflict between civicrm and jquery update drupal module.This point release has quite a few bug fixes as listed here. Some of recently added features have been included in the last release blog post

I recently completed a conversion of about 8 years of history from a 5 year old Blackbaud Kintera site to a Drupal CiviCRM solution. Confused yet? Don't worry, all we be revealed in time. As a way of giving back, I am planning to share my experiences good and bad, what worked, what did not, what I learned and what I will and won't do next time.