• Index
  • » Users
  • » alzander
  • » Posts



mtatem: Did you fix your issue?  I'm seeing the FB Connect button now.  Though, I am getting the cross-domain receiver error if I follow your link.  Try reading this post to fix that problem:
<!-- m --><a class="postlink" href="http://www.cmsmarket.com/forum/index.php?f=38&t=102&rb_v=viewtopic">http://www.cmsmarket.com/forum/index.ph ... =viewtopic</a><!-- m -->

Generally, if a template fixes the problem, it's because the 'bad' template is doing something it shouldn't be with Mootools.  Either not allowing it to be loaded, or including a different version than what comes with Joomla.  Try looking into that, and if you need help, just let us know.

Sorry for the (lengthy) delay in responding.  It's not normal, and not right.

1) Currently, the user's Facebook status is not imported into the JomSocial activity feed.  This isn't a bug with your setup, it just isn't how JFBConnect currently works.  We're just starting on some new features, and tighter integration is one of them.  I don't have a timeline for the release though.

2) This one we can help with.  Can you try the following:
In the component/com_jfbconnect/views/loginregister/tmpl/default.php file, at line 11 right under the "include_once" line, add:

defined('_JEXEC') or die();
require_once (JPATH_ROOT.DS.'components'.DS.'com_jfbconnect'.DS.'helpers'.DS.'facebookhelper.php');

Depending on how your site is configured, during the registration process, the user may not be asked for permission to post to their wall.  The above line ensures that they are (by loading the proper FB Javascript library).  After they are asked, then (if they've consented), you should see updates that they've logged in.

Let us know how this goes.

The point Ivan was making is actually that it matters whether you're using www or non-www.  Try visiting your site in each to see if one works and the other doesn't. 

This post gives information on how to fix that, and other issues, related to the FB app connect URL setup.
<!-- m --><a class="postlink" href="http://www.cmsmarket.com/forum/index.php?f=38&t=102&rb_v=viewtopic">http://www.cmsmarket.com/forum/index.ph ... =viewtopic</a><!-- m -->

Wow, not sure how we missed that, and thanks for pointing it out.  We'll make sure that fix will be in our next release.

Please provide a link for us to test with.

We've tried logging in, and when we do, we're simply left at the following page:
<!-- m --><a class="postlink" href="http://www.kite-forum.com/component/jfbconnect/?com_jfbconnect=&view=loginregister">http://www.kite-forum.com/component/jfb ... inregister</a><!-- m -->

This is likely caused by not having the "New-user Redirect" set up in the admin area.  Try setting that, and let us know.  We aren't seeing the 500 error though.

Could you PM (---->) us a temp super admin account for your site (and site address) so we can get in and debug what might be going on?

There's one other post about this going on, but it just became active again after the last post being in July.  This isn't a common problem (or hasn't been recently), but we definitely want to get to the bottom of it.

Also, what browser are you using?

We're looking into it, but don't have a timeline for it yet.  Thanks for the deprecation notice, we weren't aware of that!

We haven't tested it.  The JFBCInvite module requires JFBConnect to be present, but it may be able to work side-by-side with the extension you link to.  If you test it out, let us know the results!

Can you post your URL so we can see the exact error, or PM us your site and a temp super admin account and we can really dig in to see where the issue might be coming from.

Thanks, and we'll help you get to the bottom of it.

Sure, feel free to.  Though, if there's a problem, it's likely in your Facebook app or the FB user you're testing with.

Before I do testing, I'd recommend these 2 things:
1) Try with a 'fresh' FB user who's never connected to your site.  Who knows what info FB keeps on their end, even when you remove an app.  This will help narrow down if it's the FB user or the FB app itself that's causing issues.
2) Create a new FB app altogether. Then, update your API/Secret keys in JFBConnect and try to log in.  See what happens then.

Between the combination of the above 2 things, we should be able to narrow down where the problem lies.  If nothing works, then it may be in JFBConnect, but we're just not able to recreate that on our sites.

There isn't Javascript that checks that directly, but when you're testing on different domains, you need to make sure that you've updated your Facebook Connect URL (or create a new demo app with a new URL to test with).

Hope this helps, let us know if you run into any additional problems.

What version of JFBConnect are you using?  We haven't seen this issue since July (as can be seen from the forum post you responded too).

What is the 500 error (it says the page it was trying to reach).  Also, what version of sh404SEF are you using?  That may help us get to the bottom.

Sorry for the delay.  We haven't been on a full staff over the holidays, so mainly focusing on critical issues over the period.

We're not sure why you aren't seeing updates if you have that field approved in FB.  I just registered on your site, and got "Just joined <!-- m --><a class="postlink" href="http://www.thataudioguy.net">http://www.thataudioguy.net</a><!-- m -->" on my wall.  Do you ever get any update?

Facebook is smart enough not to post the same status to a wall repeatedly, so if your last post was "Just joined <!-- m --><a class="postlink" href="http://www.thataudioguy.net">http://www.thataudioguy.net</a><!-- m -->", and you try to register again, it won't get re-posted.

Have you tried with different Facebook accounts?  We're stumped as to why it won't post for you when you've given permission.  We're hoping to have some updates on re-requesting permission after the initial join soon.

Yes.  Actually, you should use FbClient like so:
require_once (JPATH_ROOT.DS.'components'.DS.'com_jfbconnect'.DS.'helpers'.DS.'facebookhelper.php');
$fbClient = JFBConnectFacebookHelper::getFbClient();

Then you can do things like getting the user's fb id and check if the user is logged into FB:
$fbId = $fbClient->user
if ($fbId)
// do something for logged in users

The client is a reference to the following file, so you should be able to call any functions from that file to get user's friends, photos, etc.  If you come up with something neat, let us know!

I couldn't find the login module on your dev site you posted.  However, when the button dissappears, it's usually when there's a javascript error on the page.  The FB libraries are very js based, so if there's an error in any other module, or Mootools is being prevented from loading, this can cause an issue like your seeing.

Let us know if this helps, or if you continue to run into issues.

Sorry for the delay.  Glad you figured out the redirection issues.

As for the server configuration errors, that's new to us.  The only time we've seen errors in those areas is if you're using PHP4 (PHP5 is required for the Facebook libraries, and our code, to function).  Is there a specific error your getting?  Is it a browser error or a server/php error?

If you want this figured out quicker, feel free to send us an admin login to your site.

Can you send a link to your site (you can PM it on the right if you don't want others to see it ---->).  That way we can check out the html that's being spit out and likely determine your problem. A lot of the time it's javascript conflicts or mootools issues.


Sorry, just wanted to make sure we were on the same page.  Posting to our wall is still working for us from our demo site and some other dev sites we have.

In Facebook, if you go to Settings (top right) -> application settings and then set the drop-down to "Authorized", make sure that our demo site (or whatever site you're testing) is in there and the permissions are set correctly.  If not, it obviously won't post.

We ask for permission to post to a user's wall on registration, but that can be revoked on Facebook's site in a number of ways.

Hope this helps, let us know if you figure anything out!

I think you're posting to the wrong FB component.  We don't have a "Publish stories to wall" setting and we're not posted on SourceForge.

Please verify your component. I believe you're probably talking about Joomla-Facebook which hasn't been supported/developed in over a year, and, last I checked, had a major security vulnerability.

This can happen right after you've created a new FB application, but should clear itself up shortly thereafter.  If you're continuing to see it, try logging out of Facebook, closing your browser, and re-visiting the admin area.

If you continue to see it after that, let us know.

Just so you know, on the front-end, we do checks to catch an 'session-key invalid' states and prevent the user from seeing erroneous data

We'll have to investigate this.  We use the Joomla login functionality to log the user in, which means that if you fail logging in, the same functionality that happens with the normal Joomla login modules will occur.  If it's different behavior your expecting for CB, let us know, but Joomla handles logging in just fine.

You can test what we see normally on our demo site.  Just type garbage into the login/password fields, and you'll get a red "Username and password do not match or you do not have an account yet."
<!-- m --><a class="postlink" href="http://facebook.sourcecoast.com/">http://facebook.sourcecoast.com/</a><!-- m -->

That's Joomla's standard behavior for a failed log in that we expect and use.  If yours doesn't do that, we can give you hints on how to get it working correctly.

Yes.  We check that the message is not blank when sending it, so if you just leave the "Logged in" message blank, it shouldn't post it.

Let us know if you're seeing different behavior.

Unfortunately, Facebook does not give version numbers for their API (which is royally annoying).  The 2.5.x release of JFBConnect is using a very recent one though (as of early November).

I don't know how easy it would be to implement what you're looking for as we don't use the canvas portion of Facebook very much.  If you get something up and running, we'd love to hear about it!

And to this, I'd say the best immediate option is to always redirect your users to an 'edit' page of their newly imported data.  So, yeah, we use the information from Facebook to populate their profile, but they have the chance to then edit/update/remove it.  Once they hit 'save', then it's not Facebook data anymore, it's profile data on the local site.

Getting this set up correctly to work around the ToS while still adhering to it (and allowing the user to verify the data, which is a good thing anyways), I think would be reasonable.  Setting the profile edit page as the first time user redirect page would take care of this 100%, I think.

Feel free to think through it with us.  We'd love to hear your feedback (some more).

  • 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:

Vaconi IT
Social Stream
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