Component does not work

Can you provide a URL for the page that's having issues. We'll test and let you know what we find out. Obviously, what's happening is not right...

That's definitely strange. The initial registration worked just fine, but on logging out and logging back in (in Firefox), I got a white page that looked like it was trying to forever load. Hitting refresh loaded the page just fine with me logged in. In IE8, I got the same ! error you mentioned.

Haven't seen either of these issues before.

In addition to the JFBCSocial module missing, I also noticed the top right Login to Facebook button was missing in IE. These both are good clues, and we have some ideas for a possible fix. Would you mind upgrading the "sourcecoast" account I created to Super Admin? We'd install eXtplorer (a file manager to edit our component files) and do what we can to get you going.

Thanks,
Alex

We're looking into your other issue now, just so you know. Hopefully I'll have some good news by the end of the day.

A content plugin to automatically add the comment (and possibly other) Facebook features to an article automatically is scheduled for the 3.1 release, which we're tentatively scheduling for near the end of September.

Good news. We found the issue on your site. It was with JFBConnect, but I can't say we still fully understand the issue. We've implemented a work-around and things should operate as normal on your site.

The problem dealt with our logic to decide if a 2nd Facebook permission window should show. On your site, it never will, so we disabled this check.

Please test. In the process, we disabled and re-enabled many plugins and modules, we changed your template a few times. All were in an attempt to 'not blame us' and find a conflict with some other extension. We didn't Everything should be just as we found it, but let us know if it isn't, or enable whatever we disabled.

Just so you know, we installed the "JFBConnect System Plugin" which will be a part of the 3.0 stable release. You're getting it early. No new features or anything exciting, just wanted to point it out in case you notice it.

When 3.0 stable does come out, we'll try to have a fix for this issue. However, since we can't recreate this problem on our development servers, it's possible the problem may still exist. If so, let us know, and we'll fix it much quicker next time.

Thanks!