CiviCRM Community Forums (archive)

Hi,

I've seen 3 different problems when calling API functions over the REST interface (/sites/all/modules/civicrm/extern/rest.php) in 4.0:

(1) A custom API v3 function packaged into a module, as in http://civicrm.org/blogs/totten/extending-apiv3 "Put the new files in a Drupal module and add the module to the include path", works when called via /civicrm/ajax/rest but not when called externally via /sites/all/modules/civicrm/extern/rest.php . See http://forum.civicrm.org/index.php/topic,21685.msg93964.html#msg93964 (last tested in 4.0.6).

(2) The function drupal_get_path() is not always defined, when called in a custom API v3 function accessed via /sites/all/modules/civicrm/extern/rest.php . (In this case the custom API v3 function is defined under the custom PHP directory, due to problem (1)). Tested in 4.0.8.

(3) A civicrm_post hook is not consistently called following a contact + activities being created using civicrm_api('contact', 'create', ...) by the above custom API v3 function when accessed via /sites/all/modules/civicrm/extern/rest.php . The hook is called when the custom API v3 function is called via /civicrm/ajax/rest . Tested in 4.0.8.

We've worked around (1) by putting the function under the custom PHP dir, worked around (2) for now with a nasty hard-coded path and are contemplating working around (3) by taking the code out of a hook and calling it directly from the custom API function. Would be good to find a proper solution though, any ideas welcome.

Cheers,

Dave J

Hi Lobo,

Thanks for taking a look. I've tracked down (2) and (3): CRM_Utils_System::loadBootStrap() wasn't being called in CRM_Utils_REST::loadCMSBootstrap() because no UFMatch entry was found for the contact. Now working.

Thanks again,

Dave J