"Error occurred" message

Erwin,
Definitely feel free to bump Sorry for not geting back to you today. We've been watching a few Facebook bugs that have been reported regarding different issues with the login functionality. Some were introduced yesterday with a new 'push' of the Javascript library. Another was from a few days ago and described a problem very similar to yours. We're still investigating and planning to test more tomorrow and report any issues we see to Facebook.

I don't think admin credentials are required yet, though feel free to Private Message them to us. If we find a workaround, having them will help implement and test it. From what we've observed so far, this seems to be an authentication or login-trigger issue on Facebook's side. We'll definitely let you know this weekend what we find and how likely a final solution will be. Hopefully, we'll have that for you, but I just can't guarantee it right now.

Thanks again,
Alex

Erwin,
We've done quite a bit of testing on the front-end of your site. Admin access wouldn't really help us at all from what we've found, just so you know.

Your site or your application looks be affected by an uncommon bug from Facebook itself. The bug is that when the user logs in, the 'event' that JFBConnect listens for (auth.login) is not ever being called by Facebook. Because of this, the user is logged into Facebook, but not your site. When the page reloads, the auth.login event is triggered, which is why the user is logged in then (if you have "Automatically log Facebook users in" enabled). The original report for this issue is on the page below, and it describes your problem exactly:
developers.facebook.com/bugs/292597207451952
I'd highly recommend using the "Does this repro describe your issue?" link and add information about your site and application there.

Unfortunately, you can see this bug was originally reported in December of last year. I don't know what the timeline for the fix is, but I wouldn't hold my breath right now. Since your application isn't live yet, I'd honestly recommend trying to create a new one in the Facebook Developers Area and try to use that one instead. With JFBConnect's Autotune, it should be a pretty quick process to setup. There's no guarantee that that will fix the issue, but it's certainly worth a try. There's no details in the bug report as to why some apps are affected, unfortunately, so there's not much more we can go on.

If you do create a new app, any users that have authenticated your app will need to re-authenticate when they visit again. Since your app isn't really public yet, that shouldn't be a problem.

Please let us know how that goes, and good luck!
Alex

Erwin,
I manually checked your home page and everything looks good. We stopped Autotune from following redirects temporarily, so it will only be able to test site.com/. Since yours redirects to site.com/index.php?lang=xx, Autotune will currently fail.

As for your issue, the new app didn't help with the issue. However, while I was testing, I noticed that it looks like you have the System - Cache plugin enabled with the "Use Browser Cache" option enabled. That setting may be causing the issue we're seeing because when you use browser caching, the browser can incorrectly assume that a redirect we're doing (to log the user in and return them to the current page) isn't necessary. That's because the browser says "The user's already here, let's not even reload the page, we already are displaying it and it's cached".

Can you try disabling (for now) *all* caching. Both in the Global Configuration area of Joomla and the System - Cache plugin and test again. Then, if that works, try enabling the Global Config Cache. Then, if that still works, enable the System - Cache plugin but *disable* the browser cache setting in there.

Very sorry to keep guessing at what the problem is. This is our best guess currently, and hopefully it will fix it for you. We unfortunately haven't seen this issue before though, which makes it difficult to pinpoint the cause and best fix.

As always, keep us posted,
Alex

Erwin,
Is there any way to get a super admin account to your site to test with? If you have a development site, that would work too. Unfortunately, we have no idea. I can lob ideas out all day, but really just don't know what's going on. We're very good at debugging things on-site, and that's about what's necessary now. Your subscription started in mid-May. We'll be able to issue a refund through about the end of this month. Obviously, I think we'd both rather avoid that and just fix the issue.

As for the auth.login thing, Autotune should configure that migration setting automatically to disabled. We call it something different, "Require Login Secret", because the FB name is simply confusing. In all honesty though, whether it's enabled or not won't affect JFBConnect as it's for an obscure login method that we do not use.

Thanks,
Alex

Erwin,
Thanks for the super admin access. I looked through everything on the site, but couldn't find any issues. I did disable the caching within your RocketTheme template, just so you know, but it didn't have any effect. Feel free to re-enable it if you'd like, but maybe wait until we resolve this.

I wanted to try and make a code change on your site, but wasn't able too. The file-editor extensions I wanted to install weren't working on your site for some reason. If you could, please edit the /plugins/system/jfbcsystem/jfbcsystem.php file. Around line 199, you'll see:to the below (changing auth.login to auth.authResponseChange):That switches up how the login functionality is triggered, and may help the problem on your site. No guarantees, of course, but it's a change that will likely be in our next release for a few other reasons. Would be great to know if it helps your issue as well.

Thanks,
Alex

Erwin,
Excellent idea! We've never actually created an app for a user to test on their site because it's never been something we thought would help. However, we did it on your site and it actually does seem to make a difference! Very, very strange, and I'm still very confused as to what may be different between 'your' app and 'ours'. All I did was create it, run Autotune and say "Set Recommendations".

Please test. If it works, then I can add you as an administrator to the new app. Then, you should be able to remove me as an admin (making it fully yours to do what you want with). If that's what you want to do, please add me as a friend on Facebook (alex.andreae*at*sourcecoast.com)

Thanks!
Alex