using v2 APIs from external modules

[chrism]

While looking into upgrading the Drupal CiviCRM Subscriptions module (http://drupal.org/node/234066) to use v2 APIs I had to hack some CiviCRM core code so I've either missed something or there's a bug.

- The first change needed in civicrm_subscribe.module is that crm_get_group is changed to civicrm_groups_get
- However calling civicrm_groups_get returns an error because it is not found despite a call to civicrm_initialize
- I added 'require_once 'api/v2/Group.php';' to civicrm_initialize() to allow the function to be called in the external module.

In CiviCRM 1.9, civicrm_initialize took an argument of api_required and if it was true then api/crm.php was called to include all APIs.  In CiviCRM 2.0 the api_required argument was removed and there is not file similar to crm.php that can be used to include all the v2 apis. Without the option to include APIs in  civicrm_initialize how should the API's be called from an external module?

[Donald Lobo]

People should require the specific api files they need. Including all the api files (like crm.php) loads way more files than needed

lobo

[chrism]

OK, thanks.  I thought there might have been a preferred way that folks had to keep the civicrm module's directory structure abstracted but requiring "api/v2/Group.php" for instance is straightforward.