CiviCRM Community Forums (archive)

The civicrm_subscription Drupal module built on v1 API used a contact's hash value to send a unique link that the user can click to confirm subscription (storing a copy of the hash in the module's DB records).  It used the hash value in the contact object that was returned with:

   $contact =& crm_create_contact($params);
   $hash = $contact->hash;

I am stuck figuring out how to replicate this feature with v2 api. After creating a new contact
   $contact =& civicrm_contact_add($params);

then the array returned from contact_get does not included the hash.
   $params = array('id'=>$contact['contact_id']);
   $contact =& civicrm_contact_get($params);

What is the intended use of the contact hash value? Would just creating new random hash values in the module be a suitable approach? 

Chris - On a related note, 1.9+ includes a built-in subscribe page which handles the double-opt-in (http://.../civicrm/mailing/subscribe?reset=1) - and you can add gid=x to it to limit to a specific mailing list group. Also there's a 2.1 issue to add the ability to include a Profile (e.g. other fields) in this form.

I'm wondering if this functionality is comparable to what you're using civicrm_subscription for ??

Thanks for responses Dave, Lobo.

I had missed the new /mailing/subscribe feature so glad to know about it!

After looking at /mailing/subscribe it seems like the differences are just that the subscribe module collects FirstName LastName email, has conditional behaviour based on dupe checking, and has an option for new user account creation of either CiviCRM or CiviCRM + Drupal.  I'm not sure how folks use the CiviCRM + Drupal option.

I wrote an upgrade patch for the module, but I can see that with profile inclusion in 2.1 (great feature!), perhaps some conditional behaviour (e.g. let people know if they are already subscribed) and contact matching, the module may not be needed by most.

Quote

After looking at /mailing/subscribe it seems like the differences are just that the subscribe module collects FirstName LastName email, has conditional behaviour based on dupe checking, and has an option for new user account creation of either CiviCRM or CiviCRM + Drupal.  I'm not sure how folks use the CiviCRM + Drupal option.

I think most of this functionality can be done using profiles except mailing subscription.

There is already v2.1 issue for this. http://issues.civicrm.org/jira/browse/CRM-2861

kurund

This was a little tweaky in 1.9;  we discovered it changed the current CRM user's email address as a  side effect.  Since we couldn't figure out how to turn this off, we couldn't use that feature.

Has this been fixed in 2.x?

You'll need to specifically ask for the contact hash value in the get request. The old api would return everything, which in turn made the object quite large (and involved way too many db queries)

How do you do this?
The module for subscribing in drupalv6 is in dev.
I'm modifying it so it works, but can't get the 'hash' return value.