I'm excited to report that a pretty full-featured 'phase 1' set of Pledge functionality is well on it's way to being completed and will be a part of the 2.1 release. This will fill in a significant hole in the overall CiviCRM feature-set.
Phase 1 will include the following functionality:
Record pledges received from contributors. This includes pledges for a one-time gift and pledges with regular payments spread out over a period of time.
Send pledge acknowledgments with payment schedules.
Generate payment schedules for multi-payment pledges.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
Next meet up for the UK usergroup will be at the Create Centre in Bristol on Tuesday 22nd July, 4-6pm. Thanks to Dave Moreton, Circle Interactive, and and Sean Kenny, VOSCUR, for kindly organising and donating the venue. We're keeping the agenda open and attendee led so it is of maximum use: we'll start with introductions and a couple of short presentations (volunteers, anyone?), and then follow with an open discussion/round table.
If you’re running a site using Joomla you’re no doubt aware that some things which appear to be straight forward with a Drupal base aren’t so easy. Both Joomla and Drupal have their strengths and weaknesses, I just happen to be a long way down the Joomla path.
A big issue for me was how do I restrict access to my site depending on memberships to a real world (non internet) organisation. All my members have an entry in the CiviCRM database but many will not have a CMS login. Out of the box there was no real way of achieving this without getting into LDAP territory.
Long time no blog – mostly because my initial concept of bringing the multi-language features to CiviCRM was replaced with a brand new approach, which should be much more developer-friendly.
Having the contents of a CiviCRM site in multiple languages means that certain columns in the database (the user-visible ones) must be localisable – but how to implement this from the database point of view is far from obvious.
Long time no blog – mostly because my initial concept of bringing the multi-language features to CiviCRM was replaced with a brand new approach, which should be much more developer-friendly.
Having the contents of a CiviCRM site in multiple languages means that certain columns in the database (the user-visible ones) must be localisable – but how to implement this from the database point of view is far from obvious.
The Drupal Views module has some pretty cool functionality. Views 2 fixed the "everything is a node" concept from Views 1, this enables integration with CiviCRM (which does nothing with nodes). A concise description of Views from its project page: This tool is essentially a smart query builder that, given enough information, can build the proper query, execute it, and display the results.
CiviCRM profiles (in view/search mode) behaves like views. However it is not a flexible or configurable as views is for the end user. Integrating with views also allows the potential of integrating CiviCRM information with other Drupal specific information. e.g. Contact information on folks who are most active on your blog / forum / comments
I took user.views.inc as a model and started hacking away to create civicrm.views.inc. You can get a copy of that file from our svn respository. So far its quite simple and just integrates the civicrm_contact and civicrm_email tables. I hope to add the phone/address fields in the next couple of hours/days and get a better idea of how to potentially generalize it.
We made few changes to default settings for New dedupe Now default dedupe rules settings are as follows
Fuzzy Rules for
Individual => First Name AND Last Name AND Email Organization => Organization Name OR Email Household => Household Name OR EmailStrict Rules for
Individual => Email Organization => Organization Name OR Email Household => Household Name OR EmailDue to the introduction of a new menu system in CiviCRM 2.1, my summer project got one more item on its list – the localisation of the menu entries.
Following on Lobo's recent blog post about missing features in CiviCRM - we decided to take a closer look at what it would take to get basic "Pledge" functionality added to CiviContribute (and then evaluate how soon we could take that "leap").
Due to the introduction of a new menu system in CiviCRM 2.1, my summer project got one more item on its list – the localisation of the menu entries.
