[Plugin: Simple Facebook Connect] Application access token NOT found – User ID and access token is f

You have probably an issue on your facebook application, because this plugin works pretty well.

You should test the under development version
https://plugins.svn.www.ads-software.com/simple-facebook-connect/branches/new-sfc/

Thanks for the suggestion. I just tested with that version – same result. I agree, everything else works really well. I’m just puzzled about why it can’t find the application access token.

Perhaps a typo in your url in facebook?

Another good suggestion. Everything looks good there too. I can manually publish so that’s not the issue.

Generally this happens when your webserver and PHP installation doesn’t have the OpenSSL libraries. Without those, it can’t make HTTPS (SSL) connections to Facebook.

Unfortunately, SSL is now required to talk to Facebook for most things. So you’ll have to configure your server to have OpenSSL library support. How you do that depends on your particular web hosting.

Thanks Otto – that explains it

Otto – I have php 5.2 installed using windows 2008 IIS7. I checked my php.ini under the extensions and the openssl extension is uncommented and being used. What else am I missing to get this to work? Any help would be greatly appreciated! I have the same issue as matthewccox.

[Otto] I’m encountering the same problem here. I’ve gone in and reconfigured my WAMP server and now have SSL support for the namebasedVhost I’m using where I’m having this problem with “Application Access Token not found. Cannot autopublish to Facebook Application. Try re-saving this page.”

Curious… does the SSL certificate have to be a globally recognized cert? Or, can it be a self-generated cert? In my case, currently, I’m using purely self-gen’d certs, and I suspect that may be the cause of the error, but I can’t be certain without access to the logs on Facebook’s end.

If I can get this worked out, I plan to use SFC-1.0 across 3 separate vhosts tied to 3 separate FB-App instances. Any insight you can lend is most appreciated. Thanks for all your work on SFC, by the way. Other than this one problem, it’s otherwise working great for me. ??

That’s a good point. I had not considered the certs, but that could indeed be the problem if your CA lists aren’t up to date. This wouldn’t have anything to do with *your* cert, but if your authority list doesn’t include the authority that FB’s cert is signed by, and you happen to be using the curl module for http, then curl will fail the certificate verification. I just never considered an out-of-date CA list, but that is quite probable in fact, on some hosting services.

Try the code I just committed to trunk. I added the sslverify=false flag to make it ignore the certificate verification. This is technically less secure, but it will at least let it work if your installation’s CA list isn’t up-to-date:

https://plugins.svn.www.ads-software.com/simple-facebook-connect/trunk/

Note: trunk has been heavily altered to deal with the OAuth2 migration, so you’ll need to update practically all of the PHP files, and I haven’t fully got the comments module working again yet. Sorry. It’ll be working in a week or so, because OAuth2 is being forced on all users by October 1st and I’ve gotta get this update out the door. If it makes you feel any better, I’m running this very same code on my own sites, live, to iron out the issues with it.

Cool! I’ll check it out shortly. Thanks Otto!!! ??

Thanks for the update Otto. I did not see this post until tonight, but I determined that the issues that I was having are related to the curl module that is with Windows version of php (versions 5.2.17 and 5.3.8 included).

I added sslverify=>0 to all wp_remote_get, wp_remote_post and sfc_remote calls that used https in sfc-publish.php, sfc-comments.php, and sfc-getcomm.php

This “fixed” the problem of getting the tokens, posting to fb and getting the comments back.

Thanks for working on this. I’ll also check out trunk and apply it to both my windows and linux servers.

Version 1.1 will have this fix as well.

Otto,
the codebase at “https://plugins.svn.www.ads-software.com/simple-facebook-connect/trunk/” worked like a charm! ??

I think that was exactly the problem… it simply didn’t want to accept a self-generated cert… which are really common.

Thanks for all of your great work on SFC! Mad props!

I don’t have the token.. I tried few hosting but the plugin said

No User or Access Token found. Try re-saving this page.
Application Access Token not found. Try re-saving this page.
Fan Page Access Token not found. Try re-saving this page.

So what is the potential problem of the plugin?

I am using wordpres 3.3.1 and 1.3 version of the plugin

Thanks

I have the same issue, till yesterday night everithing was good and the plugin worked really good, from tonight all my bottons desapper, i didn’t install new plugins and now

No User or Access Token found. Try re-saving this page.
Application Access Token not found. Try re-saving this page.
Fan Page Access Token not found. Try re-saving this page.

I am using wordpres 3.3.1 and 1.3 version of the plugin too!!

help!

txs