Ahhhhhhhhhhhh HA! Something you said just rang a bell in my head...
I think I know what your problem is. There's 2 things that you can try, if you would. The problem is due to a minor issue we have in the JFBConnect System plugin where a PHP warning can be spit out. While it's bad behavior on our part, it's normally not an issue because errors shouldn't be enabled on production sites.. but not all sites are in production. Anyways, PHP warnings can screw up AJAX calls. To fix, try:
Temporary solution (easy): Turning off Error Reporting. To do so, follow the instructions below, and set it to None:
www.sourcecoast.com/extensions/troublesh...ng-joomla-extensions
Permanent fix (harder): If that fixes your problem, and you still want to leave error reporting enabled, then edit the /plugins/jfbcsystem.php file. At line 40, change the following three lines like so:
if (preg_match('/\<body.*?\>/', $body, $matches)) {
$newBody = str_replace($matches[0], $matches[0] . $fbApiJs, $body);
JResponse::setBody($newBody);
}Basically, you're adding an if (xxx) { to the top line, and closing it with a } at the bottom.
If that's too confusing for you, feel free to send us super admin credentials to your site, and we can make the change.
This issue has already been fixed in our 3.2 release, due to be released later this month. We didn't put out an updated release for 3.1.x because this affects a minority of users.
Very sorry for the inconvenience, and please let us know how it goes.