JFBConnect 3.2.2 System Plugin causing pages to not render properly

Ivan,
I just went to your main site in IE8. I can see that you're running JFBConnect 3.2.2 there, but I'm not sure if you're doing this testing on another site.

Either way, I tried to log in there with Facebook and things worked normally, though I was redirected to wekiraza.remembered.com. Can you point me to the page with the issues and how to recreate it? I'm simply not sure how to restructure things properly, in all honesty, to make sure that the Facebook code (which is particular about how it's loaded already) would need to be modified to load asynchronously in addition to the asynchronous load that it's already trying. It will help to see the problem happening so I can understand further.

Thanks, and sorry for the runaround on this. I really just don't know how to fix the problem off hand.
Alex

Ivan,
I really just got to look through your page's code and noticed a few things that may, or may not, be related:
1) You're using the Share button from Facebook. This button has been deprecated by Facebook, and specifically, the sharer.php file that you're loading has been known to cause Javascript conflicts with Facebook's own library. It's possible this is part of the problem. If you can disable it, even temporarily to test, that would be great. The
Like button has all the features of the Share button and is recommended by Facebook to replace the Share button.
2) The social block of 4 things on the left may be problematic, but I don't see any reason why. Again, if you can disable it to test and see what happens, that'd be great to know how it goes.

Finally, as for re-ordering the code, you may want to try the non-asynchronous code from Facebook. It's similar to what we have, and I'm sure you can implement it instead of what we have in the jfbcsystem.php file. For information, check out Facebook's docs below which should make it pretty clear:
developers.facebook.com/docs/reference/javascript/FB.init/

If any of the above helps, or doesn't work at all, definitely let us know. Hopefully, we can get to something that works even if it means something is disabled, and then move on from there. I don't see any reason that mootools isn't loading properly, which the Javascript error from the JTabs script is saying is the problem. JFBConnect doesn't use Mootools, so it's not something we're specifically doing.

We'll get you going though.
Alex

Ivan,
The problem actually isn't that the jfbconnect.js code isn't loaded.. it's loaded just fine, and only called when the login button is clicked. The problem is that the code for the FB.init isn't being called. This is the code in the top window.fbAsync = {..} block. That code should normally be loaded after the all.js file successfully loads.. it scans for a fbAsync function defined on your page and executes it. So that's what we need to focus on on.

Now that I see the code on your page, I think you may want to remove the (function() { ... })(); code that's surrounding everything. Leaving the code inline should be fine. That will define the window.fbAsyncInit code which will then be later called after your onReady call loads the all.js library.

I still really have no idea what's causing the issue on your page, so I'm still at a loss for an exact answer, but, as always, hopefully the above solution will be the right fix. If not, is it possible to give me admin access to the site (or a developer site)?

Thanks,
Alex

Ivan,
We'll be looking again today, but unfortunately, at this point, I think we need to start narrowing down the conflicting extension. I tested in IE8 without any issue, and refreshed many times, so I'm not sure why you're seeing this issue. Have you tried on other computers?

Since no other sites have this problem, and we're adding code which we normally don't require, I'm afraid that we may be causing more problems that it's worth. If you disable the tab features on your page, does the blank page issue go away? I know before, everything with JFBConnect worked, but it was the tabs themselves that were not working. It's possible that the fix needs to go into your tabbing extension, but unfortunately, I don't know anything about what's going on with the tabs.

Have you tried contacting the tabbing extension developer and seen if they know of any issues with Javascript conflicts like this?

Thanks,
Alex