Blog posts by SarahGladstone

There is a new native extension available for allowing parents to register their children for events within CiviEvent.  Tired of using custom data fields on a child to collect information about their parents and emergency contacts?    Would you like the information collected during the event registration to create ( or update ) the various contact records needed in the back-office?  Then this is the extension for you.

I have previously blogged (http://civicrm.org/blogs/sarahgladstone/fun-and-joy-authorizenet-code-attached) and chatted about (http://forum.civicrm.org/index.php/topic,29234.0.html)  about the fun and joy related to supporting automated recurring transactions in a production environment, and started the pr

If you are using Authorize.net as your payment processor (or your clients are) for either one-time payments or automated recurring payments, then my guess is that like me you probably dread the phone call from a bookkeeper such as

"I found some Authorize.net transactions that went through and the money is in the bank, BUT there is no record of the contribution in CiviCRM.  What happened?"

I blogged a while ago about "Putting the R back in CRM" about the limits on relationships in the self-service areas.   Well I am happy to have an update.  I  (Pogstone Inc) have sponsored the creation of a new extension ( along with JMA Consulting).  This extension is taking advantage of the CiviCRM exte

I am starting a project that will allow CiviCRM to support the needs of an Australian non-profit. This non-profit is subject to the Australian Goods & Services Tax rules (GST) for some but not all transactions.

The GST requirements apply whenever the non-profit provides a tangible good or service in exchange for a payment. This is most common with their dinners, selling DVDs, and items from their gift shop. 

For anyone who is using pricesets and/or automated recurring contributions with a payment processor, you will probably enjoy the 3 custom searches that you can download here

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

Since CRM stands for Constituent Relationship Management, one would expect to have robust capabilies for dealing with relationships. This expectation is met when using the staff areas of CiviCRM.

However, in any of the self-service areas such as event registration profiles, membership profiles, and stand-alone profiles then relationships are missing.  Each profile can only be used to collect information about a single contact.

There have been a number of blog posts discussing the needs for improved accounting features in CiviCRM. The results and current specification is at the wiki at: http://wiki.civicrm.org/confluence/display/CRM/Finance+and+Accounting