- Give me the set of all household's who have a household member residing in district X. More details here. The search form can be set to just include a text box for the household name and a multi-select element for the district to restrict the search criteria
- Give me the set of contact(s) who have donated more than an input amount in this date range.
- Various combinations of AND/OR/NOT which civicrm search does not handle.
We've had captcha support for some time in CiviCRM. This is not a very popular feature since getting it to work properly is not trivial (you need the right PHP libraries and the path to the a ttf font on your server)
This seems something cool, gives us integration with yet another web service (oh what a tangled web we weave, hopefully the internet will not crash anytime soon) and avoids the whole image / font issue which we have had in the past. We also get rid of some code from the package (always a good thing!)
I'll probably hack this in when i have some free time over the next few weeks for 2.0.
In the meantime, i'm having a fair bit of fun with the new custom group / custom...Read more
The last few weeks of a release is always quite frustrating. The team is itching to get started with new development and get on with the next version. However, users are testing the beta release and filing new issues and bugs, few tweaks need to be done etc. So overall, things are in a neither here nor there status. However, once we mark a release as stable, we move most of the development team onto the new release and things get more exciting.
CiviCRM v2.0 is a big release for us internally. The current feature list for v2.0 is here. I think it will have very few bells and whistles, but will have a much improved schema and a more extensible core. Drupal has shown us the benefits of building an extensible system. I think we still have a few more revisions to go before we get there, but we are headed in the right direction. Here are some of the things that are exciting about v2.0 (IMO)
- Simplify the data model for activities by merging activity-related tables into a consolidated Activity table. Meeting, Phonecall, Activity History, Email History and SMS History will all be merged and dropped.
- Replace the use of entity_table/entity_id model with explicit foreign keys to the Contact table to improve performance on queries.
- Allow activity "creators" to assign the activity to someone else, and integrate changes made for Frontline to support multiple "assignees" for a single activity.
- Migrate useful features from the Task object into Activity - specifically the ability to set a Priority and a Due Date for an Activity.
Wes Morgan and the team at Code for change have decided to tackle something that is fairly important to quite a few medium - large sized organizations. Having support for this in CiviCRM would be really cool and we need your comments and feedback fairly quickly. Wes and team move at a very rapid pace, so please head over to the wiki page and give them and us feedback on the model and implementation. Here is the email Dave Greenberg sent to the dev list a few minutes ago:
As noted in Daniel Frishberg's post earlier today, USPIRG is kicking off a project aimed to adding features to support multi-chapter organizations. This functionality should also be applicable to hierarchical advocacy / political campaigns (national -> state -> local ... segmentation).
I'd like to strongly encourage anyone who is interested in making CiviCRM a more useful tool for multi-chapter / distributed organizations to add your questions, requirements, and any other feedback to the...Read more
- View your data via the contact view page.
- Edit your data in contact edit pages.
- Search for contacts using your data as keys.
- Access your data via Drupal modules or similar external code.
- Import and export data that...