Closed (won't fix)
Project:
Facebook Connect
Component:
Documentation
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Jan 2009 at 18:46 UTC
Updated:
14 Jul 2010 at 08:51 UTC
Invalid Argument
The Facebook Connect cross-domain receiver URL (http://www.mysite.com/modules/fbconnect/xd_receiver.html#fname=_opener&%...) must have the application's callback url (http://mysite.com) as a prefix. You can configure the callback url in the application's settings.
- Getting this pop up on IE (all version) when clicking the Connect link
The call back URL is correct.
Can anybody help?
Regards
Simon
Comments
Comment #1
klowe commentedI had this error and it was because I did not have the facebook-platform in the right place. Check out item 2 of the "Read Me" file that came with Facebook Connect
Comment #2
doyleoliver commentedKlowe - Thanks, I have checked the location of the facebook platform, and reinstalled it several times. I works fine on Safari and firefox, but not on IE?
Comment #3
burn2149 commentedI'm getting this message too, regardless of what browser I'm in.
Comment #4
klowe commentedit seems like a javascript error. did you add the line of code in your theme for IE support?
Comment #5
doyleoliver commentedburn2149 - me too, on a friends safari and it came up with the error!
Comment #6
doyleoliver commentedFound the problem!
I was using http://mysite.com to build the domain, this always autofilled when typing the domain in safari.
and I entered this as the callback on facebook developer page.
So when testing on IE I entered the http://www.mysite.com so this then caused the error!
The simple www caused the problem!
Now set up domain host to redirect to the www version of the url!
I hope this helps, and reduces problems in the future.
Comment #8
gateone commentedSadly not completely closed:
The issue still exists. Please read this information on Facebook about it: http://wiki.developers.facebook.com/index.php/Supporting_Subdomains_In_F...
The problem is that on some sites you might want to allow the user to use both www. and non-www. in your domain.
If that happens, fbconnect seems to use what the user has entered, not what has been configured in fbconnect AND in Facebook.
We would need a mandatory site's cross-domain communication channel setup that, whatever the user enteres as a domain or subdomain, the communication with Facebook takes only place on this predefined communication channel as configured in Facebook.
For the time being I simply force my users on www. whatever they enter... but ultimately this might not be such a great idea.
Apart from that: the fbconnect makes good progress, keep up the work I love it!
Steph
Comment #9
Neil Adair commentedAccording to the above reference if you set your facebook connect to use the domain "example.com" it should also work for all sub-domains including "www.example.com"
Comment #10
Cromicon commentedTry this:
http://drupal.org/node/377622
Comment #11
Neil Adair commentedFacebook connect works best if the domain is registered without the "www". Forcing "www.example.com" with htaccess just means you will not be able to use fbconnect with any other subdomains of example.com.
I can confirm that if you register example.com with facebook that subdomains work with the same api keys
Comment #12
Zarevac commentedsubscribe
Comment #13
buddaI can confirm that comment 11 is correct. You just need to set up your facebook app correctly. Probably worth noting in this modules README.txt ?
Comment #14
vectoroc commentedComment #15
vectoroc commented