IE7 Invalid Argument with JFBConnect 3.0.1

Sorry for the delay.

The 'next is not allowed' error is almost always caused by a misconfiguration of the Facebook application. Please edit your application and make sure your Site URL and Base domain are correct. The site url should be the exact home page of your site (www.domain.com/ or domain.com).

The Base domain should then be set as 'domain.com'. This lets Facebook know that any requests from www.domain.com or blah.domain.com are acceptable too. This is all in an attempt to ensure that no one tries to spoof your application.

Getting back to your error, the reason your seeing the error is because the 'next' page (which is where Facebook should send the user after they login to Facebook) doesn't appear to be part of your site (not in the site or base domain urls above). Hopefully, that's not too confusing, and helps you get to the bottom of the problem.

If not, let us know your URL. We can usually look at the code and diagnose this type of error very quickly.

Oh, finally, if you're using Artio SEF, check out the FAQ question near the bottom. It could be the cause of your issue as well:
www.sourcecoast.com/extensions/jfbconnec...on-support-questions

Thanks

We just tried logging in with IE8 (haven't tried IE7 yet), and were successfully redirected to the /facebook-success page afterwards. This was a successful registration. After that, I logged out using the logout link at the bottom (the link in the module did not work). Using the FB Connect button again, we were able to successfully re-login.

Not to defer the problem, but Facebook Connect was acting up a little earlier today. The login page was taking extended periods to load for us, and we actually saw a few timeouts. We didn't see or hear from any users about the 'next is not allowed' though.

Can you try again, and possible from a different Facebook account? The user shouldn't affect things, but Facebook does treat the developer of the account differently than any other users. When you log in as the developer, you will see verbose errors about what may be wrong, whereas if you're not the app developer, when errors occur you get a generic "This application could not be accessed" type responses. Of course, you shouldn't be getting any errors at all..

Let us know, and we'll be trying from IE7 shortly as well.

Thanks,
Alex

Yup, I obviously wouldn't recommend launching with that in the current state.

We'll be trying IE7 later tonight to see if we can recreate it. I did look at the URLs, and everything looked correct. We'll take a closer look at everything again, but after we successfully logged in, I wanted to post back here before deep-diving it further.

The "An error occurred with FBRSNConnect. Please try again later." is the generic message I was talking about that you'd get if you aren't the developer. I'm assuming when you tried to login on the work-mates computer, you tried your developer account again?

Thanks for your patience.

Well color us completely confused. I just tried to log in from an IE7 computer with a different FB test account. No errors. Then I logged in with the account I had registered with earlier. Again, no problems. Other than the same IP, these are completely different computers.

Can you tell me if you were already logged into Facebook when you were trying to log in through your site? Obviously, this shouldn't be a problem, but really trying to wrap my head around it.

A few things to try. First, after looking at your Facebook Application page on Facebook.com, I noticed that your Site URL is actually the semi-secret URL you sent to me. Can you please update this to just your main site's URL: domain.com/ (no sub-directory). This shouldn't be the cause of the problem, but is a/the proper way to setup your site URL.

Additionally, if you're comfortable making a small code change, can you try the following? This will bypass the 2nd set of permission requests, as I mentioned above. It also may fix the issue since it's where the 'next' URL is specified, which is causing the error.
In the /components/com_jfbconnect/libraries/facebook.php file, at ~ line 108, there's the following code:Can you change the variable inside the {} to $loginLink, so it looks like:
Please, report your findings, cause I'm very curious to hear how this goes. I actually think the first change (changing your site URL) is the most likely culprit as it's possible IE is encoding something strangely. Then, when Facebook checks blah.com/123 to the encoded version (http%24%35%35blah%20123), it balks thinking they're different. However, I think both options have a chance at fixing the problem.

As you can probably tell though, you're in a pretty unique situation and we're drawing at straws.

Thanks!