fb request not working

Ari,
I think I see what the problem is. Your Joomla site is being run out of a subdirectory, correct? Your Facebook Canvas page is setup for the root (www.domain.com) but your Joomla site is really out of www.domain.com/blah/joomla. When the main domain is loaded by Facebook, JFBConnect isn't executing at all.

Please update your Canvas URL to be the home page of the Joomla site. Without that, JFBConnect won't detect that a user has actually hit your page at all.. it's not even running at that point.

Think that should do it for you, but if not, let us know!
Alex

Thanks for the PM. We'll have to look into why you're getting that message. To hide it, for now, we'd recommend going into your Global Configuration area and changing the Error Reporting setting to "None". That should be the normal setting for a production site anyways. We'll figure out why the notice is popping up and fix it in the next release... sorry about that.

As for the Powered By, no worries about disabling it. In all of our modules, there is a setting to "Show Powered By" or something like that. Simply disable it, and it will go away.

Hope that helps!
Alex

Ari,
When a user registers or logs into your site, there's a lot of communication back and forth between Facebook to validate the user. Additionally, if you have the profile plugins enabled, there's even more communication to get the user's profile and avatar. For registrations, there's also the additional overhead for registering the user (creating them in the database, sending emails, and some other verification). All in all, it really shouldn't be that slow, but depending on your host, your speed with communicating to Facebook, and some other factors, things can always get a little bogged down.

I'd recommend trying to disable any of the Profile Plugins for JFBConnect first and see if that has an improvement. If so, make sure you need that plugin enabled. Other things are to check any other User plugins you may have enabled as they may be adding additional overhead to the login process. There's only so much we can do to minimize the time, though we do have some improvements in that area coming for JFBConnect v4.2 However, if it's really slow now, don't expect 4.2 to radically speed things up.. there's always some incremental improvements we try to get in each release, but our login flow is pretty optimized right now.

Hope that helps get you started looking for some bottlenecks. As you narrow things down, if you find a specific setting or plugin that is the main culprit, let us know and we can definitely investigate further.

Thanks,
Alex

The profile plugins are enabled in the Plugin Manager. You can use the filters in the top right of that page to filter for 'jfbcprofiles' plugins, and simply unpublish any that you have enabled. Once unpublished, user profile information won't be imported, so it may not be a final solution, but it will help narrow down whether a large slow down is caused by using them.

It's possible you don't have any jfbcprofile plugins enabled, if you aren't using Community Builder, JomSocial, Kunena, K2, or Agora.. if not, don't worry about this.

For the popup, we're looking into something like that to see if it's possible. I don't know when we could get it out though. We're working on the v4.2 release right now, which streamlines a few things, and if it's possible, we'd love to get it in that release (due out in April), just not sure how feasible/easy it would be to do without interrupting the full registration/login flow.

Hope that helps get you started,
Alex

Ari,
I just got into the admin area to look to see if you had "Automatically Log Facebook Users In". Since you have it disabled, there's one pretty simple change you can try that we're also testing out for the 4.2 release. Can you edit the /plugins/system/jfbcsystem/jfbcsystem.php file. Search for "status" and you should find it around line 193 in the following piece of code:In that line, change 'status: true' to 'status: false'

That can shave anywhere from about .5-1s off load time due to a little bit less code loaded from Facebook, an extra check that is not done to see if the user is logged into Facebook, and a few other minor things. They all add up though, and depending on the user's connection and distance to Facebook, it may help a little. Just so you know, this change won't really affect the display of the page, but will affect the display of the page to the 'domready' signal, which is what a lot of Javascript and other events trigger off of. Just want you to know where the improvement will present itself.

There are a few other minor changes that can likely be made, but that's the biggest. When working with Facebook (or any 3rd party site), simply communicating back and forth will add time to your page load.

Other things, non-JFBConnect related, you can look at are:
* Reducing the abundance of extra JS and CSS files loaded (there's 5 CSS and a few JS files from jReviews, a bunch of inline styles from RocketTheme as well as some compressed CSS and JS, etc).
* Enabling the System - Cache plugin to turn on full-page caching. This can cause other issues, so test that everything works for guest users. The system - cache plugin has no effect on logged in users.

Hope that helps. Let us know how it goes!
Alex