Talk:Connect/Setting Up Your Site

From Facebook Developer Wiki

Jump to: navigation, search

Step 7: "Email either your application ID or its API key to your Facebook contact so your application can access Facebook Connect functionality. Also, in order to see the new login flow pages, you must provide us the user IDs of every person testing it."

This sounds like it probably only applied to the pre-f8-launch crowd. Can anyone verify this? 776158039 16:06, 30 July 2008 (PDT)

Yes, that was for the beta version. --Pete 563683308 13:09, 6 November 2008 (PST)

in the basic steps, is anything supposed to happen after clicking on the facebook connect button? or are these steps only for showing the button?

The basic steps allow a user (who is listed as a developer of your application -- this is for the beta only) to connect accounts between Facebook and your site. -- Pete (User:563683308)


In the following section:

For instance, if you had been using http://www.exampledomain.com/connect/ for all of your files, then you would replace "<relative path from root>/xd_receiver.htm" with "connect/xd_receiver.htm" (note the lack of a leading "/" -- if you had put "/connect/xd_receiver.htm", it wouldn't work). All this script is doing is telling Facebook that you might want to render XFBML on your site, so it should load all necessary resources in order to do that.

This would be correct if the callback URL were http://www.exampledomain.com/ but previously, it was stated that the callback URL was http://www.exampledomain.com/connect/ In that case, the correct pathname/filename should just be "xd_receiver.htm" -- John User:680735216


In trying this out today 09/07/08, I'm seeing that http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php is unavailable (connection reset by peer). Makes using FB connect impossible. -- Will K

Contents

[edit] logout of my site forces facebook logout too?

Perhaps I am missing something, but if I use facebook connect, it seems impossible to have users of my site logout, without also logging out of facebook. This is far form ideal and completely counter intuitive for my users. It seems facebook connect is making use of the same facebook session cookie as facebook.com itself (is this correct?). It would be better if facebook did not set/check their session cookie and just sent a notification upon success/failure(too many tries) so that my application can manage its own session independent of facebook, either that or offer something akin to an ldap authentication service for facebook users. My only choices seem to be: dont logout of my site at all. log out of my site but dont log out of facebook (in which case as long as a facebook session remains valid anyone can come along and enter my site without a password from that machine as the current facebook user). Or, force my clients to logout of facebook when they log out of my application. None of these options are very appealing. please help?

Yes, this is by design -- when a user logs out of a Connect site, the user is also logged out of Facebook. See Authenticating_Users_on_Facebook#Logging_Users_Out_of_Your_Site for links to the appropriate calls to make. --Pete 563683308 13:07, 6 November 2008 (PST)

I think this 'design' needs amending.

We've thought about this 'design' and came to this decision because we're keeping our users' privacy paramount. Consider the case where the user is on a public computer -- at an internet cafe for example. If the user spends a lot of time on your site, then logs out of your site, they have to take the extra and deliberate step of logging out of Facebook. If the user forgets, then their Facebook session is still active for the next person who uses that computer. -- Pete (563683308 11:01, 1 December 2008 (PST))
I agree the design here is counter-intuitive. If it was made so logging into the FBC site didn't cause a user to log into Facebook then you could do logging out from apps without logging out from facebook -- 511600025 20:18, 10 July 2009 (PDT)
If the user isn't logged in to Facebook, then you won't get a user session, so you won't get any user data to display on your site, you won't be able to let the user find his or her Facebook friends on your site, and your site won't be able to publish back to Facebook. You'd have to store a lot of user information beyond the point allowed by our policies, and you could have user data on your site that's out of sync with Facebook. Pete (563683308 20:36, 10 July 2009 (PDT))
But it shouldn't be whether you are logged into facebook or not, it should be whether you have a FBC session for each individual site. And FBC sessions should be expirable without logging out of facebook. At least that is what the users of my site (who may have multiple accounts with only one of them linked to facebook) are demanding of me, and I can't provide. -- 511600025 23:28, 10 July 2009 (PDT)

[edit] therunaround script not working?

I am using the runaround scripts on the domain http://www.endivian.com/connect/ however after I click the connect button and login nothing happens. What could I possibly be doing wrong? I have the config file set up and I have the register id. The receiver is located in the connect folder and the callback url is www.endivian.com/connect/ It should be returning to the callback url but it is not..

[edit] Having Safari/IE7 Problems?

I found that once you go beyond the simple demo by adding in ifUserConnected and ifUserNotConnected callbacks to the FB.init call, that callbacks were not getting called on Safari, and sometimes, a javascript error would occur in IE7. This seeemed to be fixed by wrapping the FB.init call in a call to FB_RequireFeatures(["XFBML"], function() {...});

[edit] logo max size is 76x76 pixels

documentation needs update to indicate logo max size is 76x76 pixels

That's the application logo, the one that appears on the About page and in the directory. The Connect logo is different and is 99x22 pixels. You add it on the Connect tab. -- Pete (563683308 00:26, 18 January 2009 (PST))

[edit] Update Please

The 'Callback URL' field has been removed from the 'Basic' tab. Can we please update the instructions to reflect these changes?

reference