CiviCRM Community Forums (archive)

In CiviCRM 3.4 branch (from SVN), API v3 returns the error, "Mandatory key(s) missing from params array: hash, time_stamp" when called as follows if those keys are not included in $params:
civicrm_api('mailing_group', 'event_subscribe', $params);
I don't think the API should be requiring these keys. Populating these keys with dummy values allows things to continue normally, though I'm not at all sure of side effects.

If I understand this correctly, the problem seems to be that the API function is allowing DAO required fields to be considered as required, even though they're not really all required in the API context.  If that's right, a patch like this might be the right solution, or at least a starting point:

Index: api/v3/MailingGroup.php
===================================================================
--- api/v3/MailingGroup.php (revision 35591)
+++ api/v3/MailingGroup.php (working copy)
@@ -136,7 +136,7 @@
 function civicrm_api3_mailing_group_event_subscribe($params)
 {
 
-        civicrm_api3_verify_mandatory ( $params,'CRM_Mailing_Event_DAO_Subscribe', array('email', 'group_id') );
+        civicrm_api3_verify_mandatory ( $params,'CRM_Mailing_Event_DAO_Subscribe', array('email', 'group_id', 'contact_id'), FALSE );
           
         $email      = $params['email'];
         $group_id   = $params['group_id'];


Should CRM_Mailing_Event_DAO_Subscribe have the fields hash, time_stamp as mantory in the first place?

If not, fix the xml DAO definition and leave the code like that.

X+