Because of the way the synchronization process works with the UF_Match table, deleting records can be tricky business. If done in the incorrect order, your CiviCRM database can end up with a bunch of Junk contact records. Below is a best practice process for removing records, first the Drupal user record should be deleted then the CiviCRM record.
Process to Follow
Step 1 - Identify the Identify the Contact record(s) to be merged/removed in CiviCRM and note the Drupal User ID for the record to be removed.
Step 2 - Search for and locate the Drupal record for the CiviCRM Contact you are deleting that you identified in Step 1 and use the Cancel Account button to delete the Drupal User record.
Step 3 - Go back to CiviCRM and merge/delete the CiviCRM Contact record.
- Identify the Contact record(s) to be merged/removed in CiviCRM.
- Determine the record which is to be removed and note the Drupal User ID....
I love CiviCRM, but sometimes visualising and 'reporting' on data can be a complicated process and personally I think the Drupal Views module is a perfect way of easily generating listings and reports that can be filtered, sorted and manipulated on the fly by non-technical users.
Currently, Views intergration is pretty good but there's more work to do and I'm taking over the views maintenance of CiviCRM, to not only fix bugs, but also add enhahncements and features.
Let me know what you're looking for either in the comments or by creating an issue and tagging it 'views3' and we'll see what we can all accomplish.
Example Use Case
This example is a one event page which has tabs of many types of content and views attached which allows a anonymous user to view the info, see registered participants, register for the CiviCRM event via one webform which also automatically creates a contact, membership, active drupal user, and participant event registration to the event, logs in the user, and sets his user entered password via text field on the webform. Skvare has developed similar solutions for clients using these methods.
Using this method you can create easily customizable membership join, and event registration pages which leverage the full gauntlet of advanced Drupal 7 modules, and the ease of customizing the layout and style with css in the Drupal theme.
Original blog posted at Skvare.com.
CiviCRM 4.4.alpha3 was released today, and there's a shiny new beta release of Webform-CiviCRM-Integration 4 to go with it. Here's what's new in Webform-Integration land:
It's awesome that unlike profile forms, Webforms allow you to put more than one contact on the form. But after you've got a dozen or so, you start lose track of "what they heck are they all for?" This handy feature lets you give them more descriptive labels than "Contact 1" and "Contact 12."
Finally you can add and renew memberships via Webforms. This allows your users to sign up, renew, or upgrade their membership(s) as well as those of their spouse,...Read more
The second alpha release of CiviCRM 4.4 is now available for downloading AND you can try it out on the 4.4 sandbox site!
We Need You to Try it Out!
Excited to try the new features in this release? Please do! Great software requires great testers, and you can help. You don't need to be super technical to participate in this way, but your participation will make a huge difference.
- Download it and either do a fresh install or (better yet) upgrade a test copy of your existing database. Note that this is alpha software and should not be used on production servers.
- Try to break it! Do all the things you normally do with CiviCRM, try out as much as you can think of.
- If anything doesn't seem right, please let us know on the ...
WORKING TOWARDS DEVELOPING A CIVICRM COMMUNITY IN MEXICO
Mónica Tapia-Alvarez and Isobel Platts-Dunn
In 2009, with Common Cause International technical assistance and while developing a new citizen advocacy model for educational reform, we assessed the importance of IT solutions for managing members, petitions and donations from a large number of citizens. The IT solutions that US-based organizations used were discarded because their license was extremely expensive for Latin American organizations (Convio annual license cost is around US$50,000) and had in-built US representatives and media that was useless for Latin American contexts.
Through searching for different tools (a search suggested by...Read more
If you use the Drupal Webform-CiviCRM Integration module, pay attention for a sec, you're going to want to know this:
In order to keep up with the evolution of CiviCRM and the Webform module, I've forked the Webform-CiviCRM Integration project and started work on version 4. It will be compatible with the upcoming Webform 4 and CiviCRM 4.4 (a nice convergence of the number 4). Version 3 of this module will not work with those, so when you upgrade one of those modules, you'll need to upgrade the other 2 as well. If that's not making sense, here it is in a table:
|Version 2 works with:||6...|
With the 4.3 upgrade, the Progressive Technology Project has made a number of important steps toward breaking out our work into pieces that others can use on their sites. This blog will begin a series of (hopefully) weekly blogs outlining new functionality that others can use.
Our first blog features the civicrm_petition_email Drupal module. Thanks to the hard work of agh1, a Drupal 6 version of the module is available (https://github.com/agh1/civicrm_petition_email). We just finished porting it to Drupal 7.
For the impatient:
git clone git://git.progressivetech.org/powerbase/civicrm_petition_email
git checkout 7.x-1.x
With this module enabled, there are a few new checkboxes on the petition form that allow you to specify the name and email address of a target that should get notified every time the petition is filled out. In addition, you can optionally specify a field in the petition...Read more