Hi.
I have green messages on both module and Gigya site setup API keys "Gigya validated properly"
And testing the 6.x--2-0-ALPHA6 (auto patched version) so that the test link at popups api work though it works Gigya hasn't been able to pull it up:
Looking at gigya settings page the LoginUI container ID:: * div ID for loginUI is set for "divConnect"
I am setting as the same id (named "popups" and trying trigging from new ID ). This looks like 1995.
I also can't find where to allow anonymous users to access the popup even authenticated as user 1
Perhaps Jquery would be better solution since they are in code freeze and are very robust solution.
Although "This site is authorized to use Gigya services", Yahoo and Facebook are giving "Page not found" error's on client side.
Comments
Comment #1
theresab commentedJorge.
Went to you site and tried to login with my facebook and saw what your talking about. Are you using the 6.x-1.0-beta6 version of the gigya socialize module?
In your admin settings for gigya do you have "Use facebook connect for facebook users?" checked under Parameters for Login UIConfig /Advanced LoginUI Settings and did you follow the instructions that are in a hyperlink right under that option?
You said you had the editconnectionsUI container ID:: set to divConnect but what do you mean when you say, "I am setting as the same id (named "popups" and trying trigging from new ID )." ?
I ask because I noticed that your gigya login is in div.gigya-login > div #popups > embed #popups_Gigya.Socialize.Login where as mine (which does work) is in div.gigya-login > div #divConnect > embed #divConnect_Gigya.Socialize.Login
So I am curious what you did to change that exactly.
Theresa
Comment #2
Yorgg commentedI'm sorry beta 5 my mistake beta 6 has been released and I have updated.
I have also followed the use "facebook connect", and have follow the new application and updated the app keys at gigya.com
I have changed the CSS ID to match the popups test css div name (which is the only one working) but unfortunately did not. I will try the modal frame back to "divConnect" and "popups" and check it's not cache and try again.
Currently, the FB login link is giving a url causing a white screen.
the url is appended was: ?q=socialize-loginUID=_gid_T8L7hRtd4htaC7hOH68mNQ%3D%3D&signature=WFpyWoO%2Fv4tidQE56McrMSyF39o%3D×tamp=2009-10-23 01%3A40%3A36
Many Thanks,
Jorge.
Comment #3
theresab commentedSo does this mean you got it working now?
Comment #4
Yorgg commentedNo.
I am using Firefox 3 for configuration and Opera for the client side to separate any caching issue it may occur.
I have updated to Alpha 7 and will be trying better again 1 more time.
Comment #5
Gigya commentedThis should be fixed with beta 9. currently Gigya's system doesn't use the "use Facebook connect" parameter.
If you still encounter issues like this, feel free to open up this thread or contact us.
Thanks,
The Gigya Team