Keep refreshing on Registration Page

JFBConnect doesn't treat 'new' users any different than 'old' users, so that shouldn't be related. As for the session, definitely when you close your browser, some cookies will get erased. That will cause them to be recreated when you go to certain websites. That's almost surely related to the problem you're seeing, but I'm simply unsure why it's different for you than me.

Can you try reverting the change on your site back to the authResposneChanged method and let me know when done. I'd like to try to see if I can recreate the inability to logout. That will tell me a lot as if I can't do that, there's definitely some differences. If I can, possibly we'll look into trying to fix that issue instead.

Thanks,
Alex

Thanks. We can reproduce as well on your site. The continuous refresh (or inability to logout) are related to the same issue. We're trying to understand where things are falling apart in Facebook's Javascript library on the few sites that have this issue.

At some point this weekend, we'll be debugging further on your site. We'll need to install a file manager, like extPlorer or OSE Fileman, so that we can make some changes to test. If that's a problem, let me know.

We have a bug-fix release for JFBConnect and JLinked scheduled for next week. We'd love to have a solution to this problem for that release!

Thanks,
Alex

Wayne,
Thanks for letting us know about the issue with Chrome. That's what I use for normal browsing and haven't run into issues, but we'll check our logs to see where something may be going wrong for some users.

As for the redirect loop, after reinstalling and either a) disabling auto registration or b) trying the code fix above, let us know how that goes. We're still drilling down into why it affects a few sites (from support requests, it seems to be less than 5%). That's of course way to high, and we'll do what we can to find the best solution for our bugfix release later this week.

Thanks,
Alex

Yowser! Alright. We have a solution that should fix the issues above. Basically, Facebook looks to have introduced a (few) bugs recently into it's Javascript API. It's affecting a non-negligible amount of sites in that the 'logging in' event can be triggered on every page load. We use that event for auto-login functionality, but only expect it once, as their documentation states.

We have a workaround that will be in the 4.2.4 release that will be out anywhere from late tonight through Wednesday afternoon, depending on how testing goes. The new method will set a cookie stating if auto-logging in has already occurred and if so, will prevent another auto-login for however long your session is set for. It's not foolproof as the user could be logged back in if they browse your website for a while after they login, but it should be good.

Morpheus, I've implemented the fix on your site. It seems to work, but honestly, you know exactly what you're looking for, so please test. This is with the authResponseChanged code, so it should work as you want. We're still making minor mods to the code, but it will be very similar to what we did for you, so let us know if there are problems!

Thanks for your patience everyone, and hopefully auto-login functionality won't cause issues for you after the 4.2.4 release is out!

Alex