Welcome Guest   |   Member List
         Remember Me?    forgot password?
   
2 of 2
2
People Search Returning Blank String
Posted: November 04, 2009 at 12:16 PM   [ Ignore ]   [ # 16 ]  
Newbie

Total Posts: 11
Joined Oct 14, 2009

Thanks Nick!

After my webhost provider updated the curl options to include openssl it worked!

Profile
 
 
Posted: November 04, 2009 at 08:14 PM   [ Ignore ]   [ # 17 ]  
Administrator
Avatar

Total Posts: 35
Joined Jun 5, 2009

Jeff:

Please email your phpinfo (server configuration) to api[at]fellowshiptech.com and the team will have a look.

Also, have you tried our test harness and verified your key?
You can access it here

Give that a shot and let us know what the results are.

Profile
 
 
Posted: November 06, 2009 at 10:16 AM   [ Ignore ]   [ # 18 ]  
Newbie

Total Posts: 14
Joined Aug 14, 2009

Thanks, Nick.  I had not seen the harness before.

It is saying my tokens are not set.

I tried it for 2nd portal and weblink and 3rd party.

I’m emailing the code, too.

Profile
 
 
Posted: November 11, 2009 at 02:46 PM   [ Ignore ]   [ # 19 ]  
Newbie

Total Posts: 14
Joined Aug 14, 2009

2 interesting finds:

1) Test harness works if I enter my church code in all lowercase.

2) After I got the harness to work, I tried putting in the URL that the harness used (see “Content Location”):
http://[church code].staging.fellowshiponeapi.com/v1/People/[my record id]
into my code and it worked!

So I’m connecting OK (as evidenced by the tokens and the /v1/People/{id}), but still having trouble with /v1/People/Search.

Getting closer. smile

Profile
 
 
Posted: November 16, 2009 at 12:52 PM   [ Ignore ]   [ # 20 ]  
Newbie

Total Posts: 14
Joined Aug 14, 2009

It looks like the problem is with my Godaddy hosting (Deluxe Linux package).  I copied my files to 2 other web hosting servers I work with (Readyhosting and IXWebhosting) and they worked fine.  So it looks like I need to talk to Godaddy next.

Anyone else using Godaddy?

Profile
 
 
Posted: November 16, 2009 at 05:59 PM   [ Ignore ]   [ # 21 ]  
Newbie

Total Posts: 14
Joined Aug 14, 2009

PRAISE THE LORD! EUREKA! and <INSERT MANIACAL LAUGHTER HERE>

I found the answer to keep the GET request from turning to a POST request on Godaddy.

In OAuthClient.php, around line 186, look for this code:
     

if( $httpMethod == "POST" || $httpMethod == "PUT"{
            curl_setopt
$this->connectionCURLOPT_POSTtrue );
            if(
strlen($requestBody) > 0)
            
curl_setopt$this->connectionCURLOPT_POSTFIELDS$requestBody );
        
else {
            curl_setopt
$this->connectionCURLOPT_POSTfalse );
        

and after the curl_setopt after the “else” add:

curl_setopt$this->connectionCURLOPT_HTTPGETtrue ); 

so you get:

if( $httpMethod == "POST" || $httpMethod == "PUT"{
            curl_setopt
$this->connectionCURLOPT_POSTtrue );
            if(
strlen($requestBody) > 0)
            
curl_setopt$this->connectionCURLOPT_POSTFIELDS$requestBody );
        
else {
            curl_setopt
$this->connectionCURLOPT_POSTfalse );
        
curl_setopt$this->connectionCURLOPT_HTTPGETtrue ); // add this line
        

I don’t know if just setting CURLOPT_POST to false wasn’t enough for Godaddy or Godaddy had CURLOPT_HTTPGET set to FALSE in the first place or what was going on.

Profile
 
 
   
2 of 2
2
 
RSS 2.0     Atom Feed