CiviCRM Community Forums (archive)

I'm encountering an odd situation an am not sure if it's me or a bug in the civicrm code.

I'm trying to use the API's to retrieve information from Civi for integration into a php app that I'm developing.  I'm finding the following situation.

Calling the API for notes works fine for both Drupal and Wordpress instances for CiviCRM
 $result = civicrm_api3('Note', 'get', array('sequential' => 1,'id' => 37,));

Calling the API for contacts works for Drupal but NOT for Wordpress
$result = civicrm_api3('Contact', 'get', array('sequential' => 1,'last_name' => "Geoffrion",));
   Drupal returns the contact info for the person with that last name (me)
   Wordpress returns nothing -- no data and no error message.

Both Civicrm instances are running 4.5.4 code and their contents are essentially the same since we are working on transitioning the site from Drupal to WordPress.  The php code I am running is identical.  I just change the one line you see above.

Is anyone else experiencing a similar API problem with WordPress Civicrm?

Is this a known limitation of the WordPress instance or should this be reported as a bug?
(e.g. I know that WP's support for hooks is more limited than in Drupal)

Yes,   I found that helpful in setting the parameters.

That looks like it might be a Drupal-based instance, however.

Whatever is going on, it's specific to the contact portion of the WordPress API.  It works as expected if I use the API to retrieve note, email, or address information.

Thanks.    Interesting, it works there with no problem.

I have two WP Civi instances running on different hosts with different data.   Both show the same pattern WRT failing for contacts but working fine for everything else.  In both, the normal Civi work done via the web pages works fine.

Any suggestions for what I should be chasing down to find out why there is this selective error?

BTW...   Here's the fix...

Two constants must be defined:
define('ABSPATH' , "/web/wordpress/");   <--  place here the path to your WordPress installation
define('WPINC' , "wp-includes");     <-- this only needs to change if you've renamed the includes directory

Apparently, the contact lookup needs to include code from the wp-includes directory, while the other searches do not need it.

It might be worth adding this type of info to the documentation -- including the corresponding adjustments for the other CMS's.