17 Dec 2011

Facebook Connect Update

Just a quick note. If you are using our Facebook Connect integration, please update your Facebook Connect API Key in your Comment Settings and use your Facebook APP ID instead.

Complete instructions are available in your Comment Settings page, and you can access your Facebook APP ID at https://developers.facebook.com/apps.

You may need to clear your browser cookies and cache when you’re done. We have some great instructions on how to do that here.

That should do the trick! Feel free to leave a comment with any questions about this change.

———
Update – If Facebook Connect still doesn’t work after you update your API Key to use your APP ID, then it’s likely that you will need to refresh cache for your comments. The easiest way to do that is to post a new comment and that should force the cache to refresh.

Posted by Michael Koenig in News


Missing out on the latest IntenseDebate developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before your subscription is activated - please check your spam folder if you don't receive this.

Join 1,472 other followers

16 Comments

  1. Thanks. I checked and my APP Id and API Key are the same. Have a great weekend.

    Comment by Jeri Taira — December 17, 2011 @ 2:45 am
  2. Well something was wrong last night. I gave up went to bed and when I woke up it worked and OMG you guys made your first blog post since the dog days of summer.

    Now deciding between ID and Disqus. Not making blog posts for 5 months indicates to me not much interest in ID. It's not automatic at the moment.

    Are you throwing in the towel on this?

    Comment by callmeisaac — December 17, 2011 @ 9:07 am
  3. Hey Isaac – you're right, our blog has been extremely quiet and we plan to change that and post much more frequently. We're definitely not throwing in the towel!

    It sounds like there was a stale cache which is why it didn't work properly until this morning. I'm glad to hear everything is up and running now.

    If anyone else runs into the same issue (where Facebook Connect doesn't work even after updating your API key to use the APP ID), it's likely that the cache needs to be refreshed. The easiest way to do that is to post a new comment on your site and that should force the cache to reset. I'll update the blog post with these instructions.

    Comment by Michael — December 17, 2011 @ 7:20 pm
  4. Glad to hear it Jeri. I tested Facebook Connect on your site and it works! :)

    Comment by Michael — December 17, 2011 @ 7:23 pm
  5. That was awesome of you to do so. Thank you for taking the time to check. I appreciate that hugely.God Bless and Happy Weekend

    Comment by Jeri Taira — December 17, 2011 @ 9:21 pm
  6. So what knew features (if any are coming to ID?) How about more login options – Google, Yahoo?

    Comment by callmeisaac — December 18, 2011 @ 2:08 pm
  7. Yep, we're looking at auth options to see which ones to tackle next. Stay tuned.

    Comment by Michael — December 19, 2011 @ 7:39 pm
  8. I am still getting an error even when I changed the API key and cleared the cache. Any suggestions?

    Comment by Louie Tran — December 20, 2011 @ 7:51 pm
  9. I just sent you an email to get some more information. Please respond to that email and I'm sure we can get everything working properly. Thanks!

    Comment by Michael — December 20, 2011 @ 9:03 pm
  10. Tested seems to work OK. Facebook now asking for cloud servers to be used with apps and lead you straight onto Heroku. Did anyone sign up using that route? Seems FB requirements are becoming excessive, possible swing across to Google+. Is this going to be added?

    Comment by Joan1911 — December 29, 2011 @ 1:25 pm
  11. Been poking around for weeks trying to figure out how to get the facebook commenting hooked up on my websites and there it was all this time in the intense debate plugin I'd never checked out. Excited to see if this will engage more folks.

    Comment by yourwebchick — December 31, 2011 @ 12:21 pm
  12. Well my vote would be to auth against Google next due to current uptrends with Google+ usage – would make for more sharing of posts too

    Comment by TheGeek — January 19, 2012 @ 7:58 am
  13. +1 for Google authentication

    Comment by Paavo-Einari Kaipila — January 21, 2012 @ 11:52 am
  14. Can you please send me details and I'll take a look? It's easiest to troubleshoot via email. Thanks.

    Comment by Michael — February 3, 2012 @ 6:24 pm
  15. Hi, I seem not to get along with the Facebook integration. We've been using Intensedebate for almost a Year now, and Facebook actually never worked.

    I suddenly got the ambition to fix it today and it looks like we didnt have the API/App ID right. Changed it, even did a reinstallation, cleared the browser cache, but the Facebook Login button doesn'T even react to clicks.

    Funny thing is, i clicked on connect with twitter, an it didn'T work either. Seems to work here though.

    negativ-film.de is our url, in case you might wanna help us

    Comment by @cipriandavid — February 25, 2012 @ 12:10 am
  16. I received 52 JavaScript errors on this post, and my guess is that any number of those errors are causing the issue.

    It's probably easiest to troubleshoot this via email. Can you please email us at support [at] intensedebate [dot] com and include your Facebook Connect settings (connect URL, base domain, API key, etc)? Also, please include this link to your comment in your email.

    Thanks

    Comment by Michael — March 2, 2012 @ 6:53 pm

RSS feed for comments on this post. TrackBack URI

Sorry, the comment form is closed at this time.

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License. | IntenseDebate – Official Blog
Follow

Get every new post delivered to your Inbox.

Join 1,472 other followers

%d bloggers like this: