Upcoming Events
San Francisco CiviCRM Meetup - February 8th, 2012
February 8th, 2012
Come meet others from the Bay Area who are interested in, using or developing (more...)
UK usergroup - London meetup
February 8th, 2012
Come and meet others from the UK that are using CiviCRM or are interested in (more...)
Chicago CiviCRM Meetup
February 17th, 2012
Please join other CiviCRM users, administrators, and developers in the Chicago (more...)
London user and administrator training
February 23rd, 2012
A comprehensive two day hands on training course covering the configuration, (more...)
CiviCRM London sprint Feb 2012
February 27th, 2012
Following the CiviCRM training here in London, we will have a CiviCRM code (more...)
Philadelphia - CiviCRM Meetup for Q1 2012
March 13th, 2012
UK South West - CiviCRM Meetup
March 20th, 2012
Come meet others from the Area who are interested in, using or developing for (more...)
[Bristol, UK] user and administrator training
March 21st, 2012
A comprehensive hands on training course covering the configuration, (more...)
San Francisco user and administrator training
March 29th, 2012
A comprehensive two day hands on training course covering the configuration, (more...)
CiviCRM Usability, Test and Code Sprint - San Francisco (March 2012)
March 29th, 2012
This usability, code and test sprint is targeted at CiviCRM users and (more...)
CiviCon 2012 San Francisco Bay Area - April 2nd 2012
April 2nd, 2012
CiviCon is THE annual event bringing together the people who use, develop, (more...)
CiviCRM Documentation, Test and Code Sprint - after CiviCon San Francisco (April 2012)
April 4th, 2012
This sprint is targeted at CiviCRM users and developers who want to work on (more...)
CiviCRM Components
Tools for engaging your supporters...
Billing Information Improvements for 2.2
- Not Just a Contact Database
-
These optional components give you more power to connect and engage your supporters.
civiCASE
Case management for clients and constituents.
civiCONTRIBUTE
Online fundraising and donor management.
civiEVENT
Online event registration and participant tracking.
civiMEMBER
Online signup and membership management.
civiMAIL
Personalized email blasts and newsletters.
civiREPORT
Report generation and template management.
One of the mini-projects that we worked on during our San Francisco meetup / code sprint was improving the way name and address data is handled during payment transactions (e.g. online contributions, membership signup and event registration). Our goals were:
- Prevent name, email address and postal address information collected during a payment transaction from over-writing existing "non-billing-related" data.
- Store the billing name and address info for EACH transaction - so that it can be retrieved for audit / reconciliation purposes.
- Set a foundation for a more "shopping-cart" style interface where logged in users can select from a set of previously used billing locations.
We iterated through a number of ideas for how to meet these goals - and settled on the idea of creating a "read-only" record of address and billing name for each contribution record in the address table. This required only one simple schema change (adding an address ID to the contribution schema).
We finished a test sequence with our sample contribution page configuration - and I think we accomplished all three goals pretty nicely. That said, we still have a pretty big roadblock in the way of fully implementing the third goal - which we're leaving to 2.3 or later. In order to provide reasonable flexibility for users to create / manage a variety of billing addresses we need to get rid of our reliance on organizing contact email, postal address, phone data by "location type" - particularly the current "rule" that contacts can only have 1 address per location type. We'll be looking at this larger change in an upcoming release.
You can check out details of the changes for 2.2 in the issue tracker.
Comments
issue link
This may be the issues link that was intended for details of the changes for 2.2
Yes indeed. Fixed in the
Yes indeed. Fixed in the post now. Thx!