Getting White Screen at: user/<uid>/edit/gigya

How did you get it solved? I'm having the same problem.

Thanks for the updates. Please let us know if you see the problem again and can give the steps to reproduce it.

I'm having this problem as well, and I'm testing this on both server at home and on shared hosting account.

Which account are you using to login? Google?

I am encountering the same problem: after successfull authentication through facebook and/or myspace there is always a white screen after clicking on the "Social networks" tab in "my account". "My friends" produces the warning: "Invalid argument supplied for foreach() in [...]/sites/all/modules/gigya/gigya.pages.inc on line 223." Below there is the question: "You currently have no social network friends connected to this site. Have you connected to a social network?". Clearing cache in Safari or Firefox 3.5 does not help, neither reinstalling the module... Any hint how this problem could be solved would be very much appreciated -- thanks a lot in advance!

If you could check your gigya table for your drupal install, please see if there is a row created with the drupal uid, gigya_uid (should be a hash), and LoginProvider. If any of these three are blank, that is most likely the cause.

For users, my login provider is empty. When does that get set?

in deed, loginProvider is empty... any idea what is going wrong?

In my installation the white screen at user/edit/gigya was caused by a null session variable: $_SESSION['gigya_uid'] wasn't initialized and as a consequence function gigya_connect passed a null value to drupal_render($form)

The problem happened only when logging in from http://example.com/user/login, and not from http://example.com/user

My "Log in" menu item was pointing to "user/login", I've changed it to "user/login?destination=user" and my problem is solved (even if socialize-login seems to inherit its destination from the referring page)

i would be very very grateful if somebody could point me towards a possible solution of my white screen problem. no matter whether i use /user or /user/login there is no entry showing up in the gigya table for loginProvider. i reinstalled the module several times, even in a clean new drupal installation there seems to be only successful authentication but no connect to any social network. what am i missing?

Just for clarification, I'm getting the WSOD at /user/UID/edit/gigya, but without error messages. Just a WSOD.

In my case I isolated the problem, and submitted the details here for my situation here: http://drupal.org/node/547464. In my situation, the gigya_getUserInfo is calling the Gigya server to load the user but the response from the Gigya server is "-1, operation not permitted".

Perhaps the parameters being sent to the Gigya server are wrong...OR PERHAPS BECAUSE I was never authenticated with the Gigya server in the first place (I'm still getting an error there), then I cannot move on to the next step of getting my 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.

Just giving another data point.

I am a new install with the Beta-3 version of the module. Running Drupal 610 via an Acquia profile

I was getting the WSoD each time I went to http://example.com/user/1/edit/gigya (logged in as a Drupal user since its an old ID)

The session had been active prior to the install of Gigya. and I had a problem (at first, prob a typo) entering my key. But it's OK now.

Since I noticed the post mentioning using a diff page to Login. I logged out and then back in via http://example.com/user and now do not get the WSoD. I now get the screen showing the one social network(Twitter) I have setup so far. The original Twitter setup(getting my API Key) took a bit longer than expected time since they have been having problems for the last 2 day, but I finally created my key.

I connected to my Twitter account with no problem

When I got the failures(WSoD) there were no msgs in the Drupal or Apache logs

apologies for the noise, but i just figured out that the server time was running 15 minutes ahead. this must have caused the error... after adjusting the server to the correct time, everything works like a charm... thank you very much for the responses!

I have this working now!

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.

I was getting WSOD too. Here is a patch against HEAD (Sep 03)

--- gigya.pages.inc?revision=1.1.2.9    2009-09-08 14:45:36.000000000 -0500
+++ gigya.pages.inc     2009-09-08 16:15:16.000000000 -0500
@@ -18,7 +18,11 @@ function gigya_connect($account, $name =

   $form = array();
   gigya_login_block_js();
-  $bio = gigya_getUserInfo($_SESSION['gigya_uid']);
+  $bio = gigya_getUserInfo(_gigya_get_gid_by_uid($account->uid));
+  if (!$bio) {
+    $output = 'Error retrieving user information';
+    return $output;
+  }

   if ($bio['isLoggedIn'] == TRUE) {

The same patch is also attached, hope this helps.

I have the same problem. I'm logged in with a pre-existing user that is not connected to any networks.

After applying the above patch, I don't get a WSOD, but I do get this error: "Error retrieving user information."

Here is the info from the Gigya User (debug):

UID value :
nickname value :
photoURL value :
thumbnailURL value :
birthDay value :0
birthMonth value :0
birthYear value :0
gender value :
email value :
proxiedEmail value :
country value :
state value :
city value :
zip value :
firstName value :
lastName value :
profileURL value :
age value :
isLoggedIn value :false
isConnected value :false
isSiteUser value :false
identities value :[object Object]
timestamp value :
UIDSig value :
loginProvider value :
capabilities value :[object Object

PS - the time on my server differs from time.gov by 3 minutes.

I'm still getting this problem still too and I've applied the patch and updated. As with the poster above gives me 'Error retrieving user information'.

When we made the patch above, we intended only to avoid the WSOD. Then we found the following: Gigya expects a drupal account already authenticated with Gigya. If the user was not logged in with Gigya, then this page will return error.

Currently, there's no way of connecting a drupal account (created pre-gigya) with any social network. User account must be created linked to gigya, then it can be connected to interact with the social networks.

IMO, this is a big limitation of the module. Hopefully it will be improved in the stable release? Thanks.

Can we get a confirmation from Gigya that existing accounts can be linked with social networks in a future release? (soon)

If gigya is enabled, all users will be logged into gigya through the NotifyLogin function. Gigya authenticates ALL users to the website, regardless of if they authenticated via drupal or the social network.

For those accounts that are just plain drupal accounts, they will get passed into gigya as 'drupal-username+siteid'. The result of this will generate a gigyaUID which will be used to link the drupal user to social networks via the edit->social networks tab on the user edit page.

For accounts that use the social network to login, they will get passed into gigya as their social network+socialnetwork id + siteID.

The thing thats currently missing is the ability to synchronize a social network as an authentication method to an existing drupal user. Only new drupal users are allowed to authenticate via gigya, and these new accounts that are created aren't allowed to login via the traditional drupal authentication mechanism.

In regards to the WSOD, there are a few things that can cause this, usually a problem with the ID and signature that gigya passes back to drupal, which sometimes fails the security check. If you get the newest version of CVS, we've added more debug messages to watchdog if there is an error, and changed the return parameters for functions that call Gigya's REST api and get back errors.

That explanation is helpful, thank you.

Is it also a confirmation that existing drupal users will be able to sync with Gigya in an upcoming release (soon)?

If it's not the case, then Gigya is really only useful for new sites.

Is it also a confirmation that existing drupal users will be able to sync with Gigya in an upcoming release (soon)?

Existing Drupal site users can connect to social networks. However, they cannot use a social network for authentication.

New site users will (if the site allows it) have the option of setting up their account to authenticate with native Drupal or a social network (via Gigya) but not both. Nor will they be able to change this choice once their account is setup.

Yes, also in an upcoming release we will support authenticating using Social Networks for existing site users using a "merge" concept where users will be asked whether they want to "link" their existing Drupal site user to a new Social network identity and allow logging in with both (or even more than two if the user wishes so).

hope this helps.

The feature mentioned above - "Linking" is now available in beta8.

So authenticating using Social Networks for existing site users are asked whether they want to "link" their existing Drupal site user to a new Social network identity and allow logging in with both (or even more than two if the user wishes so).