That helps narrow things down a lot. If you enable the JFBCContent plugin by itself (without the JFBCSystem plugin) the error you see is actually a known problem. That will be fixed in the JFBConnect v6.1 release. It's obscure though as the System plugin should always be enabled.
For the system plugin, the error line number has changed from 94 to 61, which is correct. So, something obviously did change when you upgraded. That means we need to check just a few other directories and files to see where something else is going wrong.
Can you go to the /components/com_jfbconnect/libraries directory and compare the following files against the /frontend directory in the installer package:
factory.php
provider.php
provider/facebook.php
provider/google.php
provider/linkedin.php
provider/twitter.php
The factory file is what loads all of the others. The provider.php file has the onAfterInitialise function which isn't working for some reason. The /provider/xyz files may also have an onAfterInitialise function that overrides the provider.php file. My guess is that one of those files is missing/different than it should be.
If that doesn't help, we'll need to FTP into the site to narrow things down further as I'm not sure what's happening. Please PM me those credentials.
One other thing, you mention the errors are below when the system plugin is enabled:
Fatal error: Call to a member function onAfterInitialise() on a non-object in /home/kepplewr/public_html/plugins/system/jfbcsystem/jfbcsystem.php on line 61
Fatal error: Access to undeclared static property: JLoader::$classes in /home/kepplewr/public_html/libraries/loader.php on line 195
Generally, there can be only 1 fatal error on a page. At that point, it's 'fatal', and nothing else can execute.. so that's a little strange that you're seeing 2 errors.
Also, the loader.php file is a Joomla core file. The line at 195 is using a variable called $classes. The error that that is an undeclared static property is disconcerting because it's definitely declared at line 25. I'm not sure why you'd be seeing that error, but it definitely seems something may be wrong with the Joomla installation in general. Of course, we'll help investigate however we can.. but if Joomla was installed by SiteGround, they may have some ideas why that error is occurring. I was testing on Joomla 2.5.20. I'm assuming that's your version as well.
Thanks,
Alex