Sometimes I get frustrated with CiviCRM. For all the great features there are problems / limitations that we seem to keep hitting. So, if lots of people want the same things added / fixed why aren’t they being fixed?
Blogs
We have been looking at whether it is a good idea to use households and thought I would pull together the various things that have been written about households into a bit of a 'where are they at'.
Update: Due to an unfortunate error multilingual sites cannot be upgraded to CiviCRM 3.2.2; if you’re running such site please wait for CiviCRM 3.2.3. Single-language sites (regardless of the language they use) should upgrade to CiviCRM 3.2.2 cleanly, and new CiviCRM 3.2.2 installations (both single- and multilingual) should work without a problem.
CivicActions is offering a full day CiviCRM User Training in Seattle and in Berkeley.
I'll be conducting the training which is aimed at non-profit staff and consultants who want to learn how to configure, administer and use CiviCRM.
The training program is equally applicable to people who are already using CiviCRM and want to become "power users", as well as people who are interested in evaluating CiviCRM for their organization or clients.
I have developed very basic iphone app for CiviCRM using Titanium framework.
Tokens are used in CiviCRM to create mail merges in much the same way as, for example, Microsoft Office. They are currently implemented in (at least) four places in CIviCRM: 'CiviMail', 'Send Mail to Contacts', 'Create PDF Letter' and 'Create Mailing Labels'. Out of the box Civi comes with a decent set of tokens, including tokens for all the address fields. One thing it doesn't do is provide a token that correctly formats an address block taking account of when fields aren't present. For example, if i used the following address tokens for my address: