Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Here is the issue.
Gigya is installed and configured. New person logs in through Facebook and is directed to the user page where they fill in the required information.
They now are in the site and the connection to the Facebook account is established and is in the account/edit/social networks.
Now the person logs out of the site and we see that it disconnects them from Facebook.
The person tries to log into the site by clicking the social network icon for face book and after the connection to face book is established in the pop up they are brought to the very same page they had to fill out to register with the site.
((this is the first issue as I was under the impression that after they had done this then from now own they could log into the site through this method))
So now they put in the user name and password they created in the first part and hit enter and the following error code comes up.
• warning: Invalid argument supplied for foreach() in /mnt/target03/360581/www.ractivestudios.net/web/content/includes/common.inc on line 914.
• warning: strtr() [function.strtr <http://www.ractivestudios.net/function.strtr> ]: The second argument is not an array in /mnt/target03/360581/www.ractivestudios.net/web/content/includes/common.inc on line 931.
Now if they return to the home page and use the Drupal login their with their username and password and they are now in the site and we see that the site connects their Facebook account.
Is this the way it is supposed to work? If not then what do I need to do so that AFTER a person has used their Facebook to sign up in our site that they can continue to just connect to the site via that? Or do I need to place verbiage telling them NOT to try and use the Facebook icon and log into the sight with the username and password they supplied when they first signed up using their Facebook account?
I hope I have explained the problem.
Theresa
Comments
Comment #1
theresab commentedTo clarify, this is a fresh installation of Drupal, with only the gigya module and needed supporting modules (like the patched popup module) installed along with VIEWS and CCK. No members where signed in before the installation and set up of the modules. The site is for development right now solely to test the gigya module and social networking.
The problem is not with logging into the social network but rather after a person uses the social network to log on for the first time and fills in the username and password for Drupal that they MUST after ward use the Drupal user name and password to log into the site as opposed to just clicking the Facebook icon and once connection with Facebook is established being logged into the site with out also having to put in their username and password for Drupal.
I hope this helps explain the situation.
Comment #2
theresab commentedOk some more information.
I notice that when I look at the Gigya table in the database that all the fields
( uid | gigya_uid | loginProvider | avatar_timestamp )
are empty. I would think I should each person's that signed up through the Social Network login uid, and other information, in this table.
Any thoughts?
Comment #3
blasthaus commentedsame issue, subscribing here.
Comment #4
mdorman commentedI'm having the same issue. I have a few existing users that I had created using Facebook accounts during early testing. However with the latest release I'm not having any luck linking new users. As mentioned above I get a full Drupal registration page after ending up on /socialize-login?UID=.....
Comment #5
theresab commentedJust dug through watch dog and I find this for each gigya entry
Hope this helps.
Comment #6
8ballsaysiwin commentedsubscribing. Having same issue here. At first I thought that it was because I had not created a FB application, so I did that, but still ran into same problem.
Comment #7
vermario commentedSame issue here, the user is brought again to the registration form...
Comment #8
japerrythere was an issue with beta5 that was causing this. Please update to beta6 asap, it should fix this problem!
Comment #9
theresab commentedI have just installed the beta six and did a test and after I was used my facebook account to sign in for the site time i was redirected to the registration page where I entered my user name an email account and then submitted and I received this warning:
But I was logged on so I logged out and logged in via my face book account and was in the site with a warning and without being redirected to the sign up page once more.
So the module is working but there is that warning.
Comment #10
mdorman commentedHi, beta6 worked for us as well. We've implemented it on a new site with ~3500 existing members: http://www.tagsellit.com We'll have to see how they take to the idea that only new users get to use the full functionality.
Comment #11
acouch commentedhaving same problem with beta6.
i can also confirm that nothing is getting written to the gigya table when registering through facebook.
it looks like the gigya_save_profile function isn't getting the right $edit info or isn't writing to mysql correctly.
Comment #12
azinck commentedI'm still seeing the problem exactly as described with beta6. But I see the problem using google as well as FB. (and those are the only two services I've tried).
Comment #13
azinck commentedI'm continuing to investigate this. I've found on my setup the call to user_save() on line 102 of gigya.pages.inc is causing an immediate redirect to /user that's preventing all the code following that from being executed.
Comment #14
azinck commentedFinally figured it out and I feel a little dumb.
Turns out the problem is that I had created a Triggered Rule (with the Rules module) long ago that redirected to the /user page after saving a profile change. I removed that and of course it works just fine for both Google and Facebook.
Comment #15
Gigya commentedThis should be fixed now with Beta8, which we will release today.