So I've tested this more than once, and when logging in via HTTP I'm not getting the refresh to update session from the iFrame app. After manual refresh of page all is fine until I visit http content page and try to post a comment which is to be shared on FB and I get a white screen ads only. When I test post comments and share to FB on HTTPS same content page the function works perfectly.

I have symbolic links to the https, and when secure browsing option is opted into by the user there is never an issue because all content is being served to HTTPS however when opt-in HTTPS isn't selected all content is served via HTTP.

I along with another developer have looked and looked for a solution but haven't found anything that appears to be a like issue unless we missed something.

When reviewing the console for errors when using HTTP instance nothing is in error, and after a hard refresh the node reloads and we get the share on fb box popup which posts fine it's just the disconnect from time of pressing save to reloading the node and revealing the popup for sharing on fb. I have tried without having the share on fb box check without any success.

Every once in awhile the following console error will appear though:

Request URL:http://1.203.channel.facebook.com/x/3143674217/1376940354/true/p_100002264149140=0
Request Headers
Referer:http://1.203.channel.facebook.com/iframe/11?r=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%2Fv1%2Fyp%2Fr%2FUb2OCc5xWCb.js&r=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%2Fv1%2Fy2%2Fr%2F
5JYpOIBpYgo.js&r=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%2Fv1%2FyV%2Fr%2FWnFdnhQBvpd.js&r=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%2Fv
1%2Fyl%2Fr%2FWVRx1MI9uJj.js&r=http%3A%2F%2Fstatic.ak.fbcdn.net%2Frsrc.php%2Fv1%2FyI%2Fr%2FTF8WVXsmqcX.js

User-Agent:Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_7; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3

URL above is one full URL but to avoid run off of page I did a hard return.

When I can provide more information I will but that's what I have for now without a solution in site, and again all this happens only from HTTP URL instances but works 100% perfectly when accessing via HTTPS.

Comments

joshuabud’s picture

joshuabud commented

I apologize for adding a comment so quickly but I just tried FB connect from HTTPS and it did not work as it required a hard refresh to allow login to take place again from FB connect within app. Also noticed when logging out that I had to refresh the page to recognize the logout from FB just before logging back in to test the HTTPS login functionality.

Dave Cohen’s picture

Dave Cohen commented

I would start with the usual, check logs and use firebug to look for javascript errors. You might even use a packet sniffer on your machine to look for some harder to find problems.

I have a hard time following what's related to http vs https. Maybe its not related to that?

bonked’s picture

bonked commented

Looking into this more, I think this may be related to http://drupal.org/node/962130

bonked’s picture

bonked commented

A bit more info as to what is happening for us.

Chrome (Mac) is giving me this when attempting to use the facebook connect login button. The login window appears and the console begins spinning up error after error of this:

Unsafe JavaScript attempt to access frame with URL https://www.facebook.com/login.php?.... from frame with url http://our-domain.com/fb_cb/... Domains, protocols and ports must match.

This continues until you finish filling in the login form.

Then, the window closes and you get the following:

XMLHttpRequest cannot load https://our-domain.com/fb_cb/..../fb/ajax/session_change. Origin http://our-domain.com is not allowed by Access-Control-Allow-Origin

And 

Uncaught SyntaxError: Not enough arguments fb.js 223

I think this is what is preventing the page refresh. I am sure it has to do with the limitations introduced by jumping from http to https. I'm at a bit of loss of how to correct the issue though. Using the latest 6.x-3.x-dev

Dave Cohen’s picture

Dave Cohen commented

The SyntaxError might be a bug in modules/fb. The cannot load error is the underlying cause of the problem. I don't understand why the errors says both "http" and "https".

drubage’s picture

drubage commented

We are also seeing this error where the page does not reload after logging in/creating an account via FB. Any ideas? We get this:

Error: uncaught exception: [Exception... "Not enough arguments [nsIXMLHttpRequest.getResponseHeader]" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: http://www.paysage.com/sites/all/modules/contrib/fb/fb.js?x :: :: line 223" data: no]

alphageekboy’s picture

alphageekboy commented

I also see the error above in Comment #6 "Error: uncaught exception" on The 7.x-3.x-dev version.

I tried a plain Drupal 7 site with Drupal for FB and everything works fine. -So something is happening on our version. I'll post more once I have a better idea of what is going on.-

I found the error. The error happens when I have a trigger for "when user logs in". This trigger redirects the user to the front page.