Upcoming Events
NYC CiviCRM Meetup - September 7th
September 7th, 2010
This next NYC meetup will feature a case study or 2, a look at what's new in (more...)
Configuring, Customizing and Extending CiviCRM - New York
September 16th, 2010
This comprehensive two-day hands on training course is targeted at (more...)
CiviCRM User and Administrator Training - New York
September 16th, 2010
A comprehensive two day hands on training course covering the configuration, (more...)
CiviCRM Code and Test Sprint - New York
September 18th, 2010
This code and test sprint is targeted at experienced developers who want to (more...)
CiviCRM Toronto Meetup
September 21st, 2010
Come meet others from the Toronto Area who are interested in, using or (more...)
CiviCRM Philly Meetup – September 2010
September 23rd, 2010
Come meet others from the Philadelphia Area who are interested in, using or (more...)
CiviCRM Seminar - Dublin
September 28th, 2010
NfP Services are hosting a free seminar at The IBOA, Stephen St Upper, Dublin 8 (more...)
London developer and implementer training
September 30th, 2010
This comprehensive two-day hands on training course is targeted at implementers, (more...)
London user and administrator training
September 30th, 2010
A comprehensive two day hands on training course covering the configuration, (more...)
Berlin user and administrator training
October 6th, 2010
A comprehensive one day hands on training course covering the configuration, (more...)
Berlin developer and implementer training
October 7th, 2010
This comprehensive one-day hands on training course is targeted at implementers, (more...)
Benelux meetup in Brussels: Connect, communicate and activate your supporters and constituents
October 11th, 2010
Come meet others who are interested in, using or developing for CiviCRM. For (more...)
CiviCRM Toronto Meetup
October 19th, 2010
Come meet others from the Toronto Area who are interested in, using or (more...)
CiviCRM Toronto Meetup
November 16th, 2010
Come meet others from the Toronto Area who are interested in, using or (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.
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!