In user/%/edit/gigya I was getting a white screen.
It turns out that nothing is returned from gigya_getUserInfo.

The function gigya_getUserInfo sent:
http://socialize.api.gigya.com/socialize.getUserInfo?

QUERY STRING:
apiKey=[KEY]
timestamp=[UNIX TIME]
nonce=[SOME NUMBER]
sig=[SIG]
uid=admin

Here was the response:

code: -1
error: Operation not permitted

Comments

barobba’s picture

The function _gigya_request_failer in gigya.inc should check:

Whether $results->error exists, e.g. if($results->error) { /* do something */ }
Whether $results->code == -1

Gigya’s picture

Status: Active » Needs review

Thanks, we will review this asap.

barobba’s picture

Perhaps because I was never authenticated with the Gigya server in the first place, then I cannot move on to the next step of getting my current user's information. Is anyone having problems where the authentication is not working in the first place? That might explain why the Gigya server won't process further operations at /user/UID/edit/gigya.

It might also explain why I'm not disallowed from connecting. Because my website was attempting too many non-permitted operations.

Gigya’s picture

Status: Needs review » Closed (fixed)

Yes, that was exactly the issue and as soon as you solved the OpenID configuration the problem was solved. Thanks for the insights you provided during the process.

barobba’s picture

I have this working now!

In addition to the OpenID fix, which was a necessary step forward...

In my case, I forgot the shared hosting provider runs a firewall that uses white-listing. That explains the uncaught -1 error, and why this was not in the Gigya documentation. (Though, the switch statement in "gigya.inc" should be written to handle these general cases.)

THEN, I have a server at home and this wasn't working there, but my computer's time was off by five minutes. So, I fixed the time and voila! Two websites working with Gigya.

Thank you Jperry (et al) for your help.