• Index
  • » Users
  • » alzander
  • » Posts



What is your setting for "Create New Users"? It should be Yes, from what you state, but I just want to make sure.

A new user is getting created, as you say.  However, can you check the JFBConnect UserMap tab in the admin area?  This should show the user's Facebook user id (a long number) and their Joomla username on your site.  If there is no entry here, then that's why when you log in again it doesn't know you already have an account.

- Do you have any User plugins that perform redirects after a successful registration?  That can prevent the usermap from happening.
- What are your settings for approving new users and new user confirmation emails within CB?  Neither should be causing this issue, but it may help pinpoint the problem

Which setting are you using for "Create New Users" in JFBConnect?

I'm not sure what could be causing this.  Can you send me a link to your home page?  If that doesn't help come up with a resolution, I would need access to the admin area of your site.

The next release (due within a few days/early next week if testing progresses well) has the "Remember me" function for Joomla user's logging in through the JFBCLogin module.

I'm not sure where that's set.  We don't set the local=en_EN within the application, so my guess is that this is occurring within your FB application itself.

This bug has been fixed in the upcoming release.  We're going through testing, but are hoping to have a release out within a few days/early next week if everything goes smoothly.

We began (and still are) investigating your radio site.  It's very strange what's happening.  We've never seen the admin area say that the session is expired like it is on your site.  If we trade out your key with a development key we have, it shows the correct application and callback information.  If we use your key in one of our dev sites, it shows correctly too.  For some reason, it's like your site doesn't like the Facebook application.

The new error your describing below is caused when you're using other Facebook extensions on your site that use the Facebook php library.  This can be from JomSocial or 'fan'-type modules.

The next version of JFBConnect will properly check if the library's already been instantiated and not throw the error like it is there.  If you'd like to add the check yourself for now, you can try the following:
In the /components/helpers/facebookhelper.php file, around line 136, add the following bold statement:
if (!class_exists('FacebookRestClient'))

Sorry for the inconvenience.  We'll let you know what we determine about your other issue.

No, we haven't. Unfortunately, in this thread and another regarding image issues, we've been pleading for someone to send us some Super Admin credentials so we can get to the bottom of the problem.  We can't recreate it locally, which makes it near impossible to debug.

If you are experiencing this problem, please PM (------>) us an account for your site.  We may change some code on the JFBConnect component and install NinjaXplorer (to allow us to browse the Joomla filesystem).  That would be all.

Other post:
<!-- m --><a class="postlink" href="http://www.cmsmarket.com/forum/index.php?f=38&t=305&rb_v=viewtopic&start=10#p2106">http://www.cmsmarket.com/forum/index.ph ... t=10#p2106</a><!-- m -->

That's definitely not good/right.  I can recreate it pretty easily myself.

Can you PM me a Super Admin account for either site?  I'd like to check a few things, and test some of the new code from our upcoming release. We also may try a proven API/Secret key to see if that doesn't have the issue so that we can eliminate your FB app as a source of the problem.

Sorry for the inconvenience, but we'll get you up and running.

There's another report of a (different) issue regarding using JFBConnect with CB when "Create New Users" is set to 'no'.  We're investigating these presently, and will keep you posted as to what we find.

Thanks for the report!

We don't right now.  Unfortunately, we've been a little distracted with some other ventures recently and haven't focused on JFBConnnect like we want.  That's changing now as we're putting effort into a new release now and have plans for more features going forward.

However, the main features we shoot for are broad facebook/joomla features, not as much integration with specific components as that doesn't affect the majority of users (usually).  If you come up with something, we'd love for you to make it available/sale either through CMS Market on your own.  We'd certainly help promote it as it makes us look better too current/smile

Thanks for letting us know.  We'll add better scrubbing to our variables going forward.  I can already see what the problem is from what you state, and it's not good.

We're working on JFBConnect today.  We'll test further with the scenario you mention below (it's actually not a commonly used one, from the reports we've gotten).  If we find a cause and/or are able to reproduce, we'll let you know.

Yes, the usermapping should handle keeping users in-sync with their CB profiles.  CB does some strange things though depending on how it's configured, and we might have missed something.

Are you still getting this error?  It's usually caused in very rare circumstances when you've first installed the component, the API key and Secret key have just been created, and you were already logged into Facebook when you try to visit your site.  Facebook gets confused with the new key and throws it.  It usually resolves itself very quickly, though you may need to close your browser and re-open it.

I'm not able to see the login module on the page you link to. Let us know if the above helps clarify the issue.

That message is being shown by the using the built in Joomla Notifcation/Error message system.  If it's showing up badly, then other components will likely be showing up badly too.  Here's my suggested fix:
In your template, there's the following line:    <jdoc:include type="message" />.  Whenever any component has a notification or message to display, this is where it will display in your template.

What you should do, is update your template file to include the system.css file which has default stylings for the error/notification messages.  You can do this by adding the following line to your template file.
<link rel="stylesheet" href="/templates/system/css/system.css" type="text/css" />
Alternatively, you can copy most of the styles from that file into your template's css file and modify them to look good for your site.

Finally, if you really don't like it, you can remove that jdoc line, but we wouldn't recommend it as notifications are important for the end user from many components.

Hope this helps.

Unfortunately, the site that sent us their information has been "Taken down for legal reasons".  We really do want to get to the bottom of this issue, but again, are unable to recreate here and need a server to test with.  If you are affected, and want us to get to the bottom of the problem, please PM us your site information!

Thanks for your code snippet.  Yes, that's drastic (you shouldn't have to modify other comps to get around issues that may be from ours).  Is that working correctly for you now, or are there other issues still?

We've set aside some time over the next few days to investigate the stat_fails error message, and will hopefully have some good news by the end of the week.

Yeah, we do not touch other component's tables.  That's bad karma all around.  Glad you found the issue (and glad we weren't a part of it)  current/big_smile

You're welcome to try to hack it in there.  The reason it's not a simple pasting of code is because we have different parameters for redirecting the user, javascript that must also be called, and some library functions from the JFBConnect component that we use as well.  Connecting and interacting with Facebook is pretty complex.  We'll see if we can make a more hybrid module or some other easier method for you to use.

As for the duplicate logout button, can you 'hide' that in the cblogin module to enable you to use both?

Thanks for sending the credentials, we're planning to do an investigation into this Wed or Thurs.  I know that's not speedy, but we want to make sure we set aside enough time, because it's obviously a big issue and doing it 'here and there' won't cut it.

We'll keep you posted to what we figure out!

Are you still getting this error?  We added Facebook and your site to our trusted list (in combinations of individual or both or none) and were never able to see this error.  We also tested with our demo page.

If you can help to narrow down when this occurs, we'll gladly look into it more.  If someone else is experiencing this, please let us know.

Hehe. Not sure what I'm testing against (new or old), but the error I see when I click the blue login-button is:
The Facebook Connect cross-domain receiver URL (<!-- m --><a class="postlink" href="http://www.jasonsfitkitchen.com/?fbc_channel=1#fname=_opener&%7B%22t%22%3A3%2C%22h%22%3A%22fbCancelLogin%22%2C%22sid%22%3A%220.919%22%7D">http://www.jasonsfitkitchen.com/?fbc_ch ... .919%22%7D</a><!-- m -->) must have the application's Connect URL (http://jasonsfitkitchen.com/) as a prefix. You can configure the Connect URL in the Application Settings Editor.

That's stating that the Connect URL is set for the non-www version of your site. In the Facebook application overview, it should say something like:
Canvas Callback URL
    <!-- m --><a class="postlink" href="http://www.jasonsfitkitchen.com/">http://www.jasonsfitkitchen.com/</a><!-- m -->
Connect URL
    <!-- m --><a class="postlink" href="http://www.jasonsfitkitchen.com/">http://www.jasonsfitkitchen.com/</a><!-- m -->
Base Domain
- Since you're probably not using subdomains, try leaving this blank for now. Shouldn't matter either way though.

Verify that, and hopefully something will stand out.

There's a conflict being created between the JFBConnect component and the "Fan Box" module you're using.  If you look at the source for your page, there are two FB.init API calls:
FB.Facebook.init("7ae6bbd31e3fd8ce58039e5aa4e562b4", "/index.php?option=com_jfbconnect&view=xdreceiver&format=raw");

The first is ours, the 2nd is the other module.  Facebook (to my knowledge) only lets you initiate one API key per page.  Can you update the keys to be the same and test?

I'm getting the cross-scripting error now.  It seems like your domain is always redirecting to www (which is good), but the callback URL is set to the non-www version.  Can you update your application with the correct callback and let us know how that goes.

By trying everything in the other thread, have you tried creating a new barebones Facebook app with just the setting from the user guide and used that API/Secret key?  That always seems to solve the issue, and usually points people in the right direction of which switch they flipped in the app that they shouldn't have.

The cancel/skip problem is something we can't do much about.  Facebook isn't 'shrinking' the window if you cancel, it leaves it wider.  Since we have no way to detect that skip is pressed, we can't re-shrink the div again.

If you can post your page (or PM it to us if you don't want it publicized), we can look at giving you some hints for updating the CSS so it should work on the right side.  We never thought about this, but good idea current/smile  We may include that as an option in a future release.

Sorry for the delay in getting back to you.  I see the site is password protected again, so I'll offer what support I can here.

If no information is importing, check that you have no "Required" fields set in CB.  This causes issues if they're aren't being filled in by Facebook, and so CB doesn't properly save the profile.
Can you look in the images/comprofiler directory and see if any images in there are correctly being fetched from Facebook?

Please feel free to PM (----->) us a super admin account to your site and we can go in and take a look.

  • Index
  • » Users
  • » alzander
  • » Posts

Board Info

Board Stats
Total Topics:
Total Polls:
Total Posts:
Posts today:
User Info
Total Users:
Newest User:
Members Online:
Guests Online:

Social Stream
SourceCoast Joomla Social Extensions
Friday, 25 May 2018
JFBConnect 8.0 Coming Soon! Stay tuned.
Refer and Earn

Like our extensions? You're not alone! That's why they're used on tens of thousands of websites. Now you can earn 20% of any sale you refer to SourceCoast.com.

We provide excellent documentation, well laid out sales pages and great support. All you need to do is spread the word and we'll take care of the rest.

Learn About Our Affiliate Program