Installation quesitons

Wonderful, glad to see you as a subscriber!

Another user just reported a blank page on the overview. If you could try to do the same thing we asked of them, that would be great to help us diagnose the cause of the problem. A blank white screen is almost always the sign of a PHP Fatal Error. If you install again, can you go Site->Global Configuration and on the Server Tab change Error Reporting to "Maximum". Then hit the offending page and report any error output here. When done, turn error reporting off.

As for installation, you are only required to install the com_jfbconnect_xxxx file. That will install the JFBCLogin Module and the 2 plugins. I actually just disable the plugins from view as those shouldn't need to be downloaded and installed separately, which I can see being confusing. Everything else are optional modules to enhance your site.

Not sure if you've gone through it, but the configuration guide for JFBConnect should help you. However, with the white overview screen page, I think there's obviously a bigger problem that needs to be resolved before you'll truly be able to configure, and use, JFBConnect:
www.sourcecoast.com/extensions/jfbconnect/configuration-guide

No, that shouldn't be throwing an error like that if you don't have a key. We try to catch any fatal errors that could be caused by not having an API or Secret key installed so that it doesn't prevent execution of code.

Obviously, if you want to try obtaining an API key and inserting it into the configuration area (which you should still be able to access), that'd be great to know if it fixes the problem. If so, we'll add plenty more checks to prevent this in the future.

Thanks

Another thing to try (just saw in another post) is to try logging out of everything and clearing your cache. Not sure why it worked, in all honesty, for this user, but please feel free to try and report your results:
www.sourcecoast.com/forums/topic?id=1203&p=1#p4433

We'll be testing different things with no API key to see what happens and if we can cause the issue locally. Thanks for the feedback

We think we've fixed the issue in the new 3.0.0 release - the exception wasn't being caught properly when no app ID/API Keys are set up. If you still see the error, please let us know.