The API key is not the same as the App ID.
Go to https://www.facebook.com/developers/apps.php and get the correct information.
Holy cow – there are two different sites or something for Facebook Apps. The one linked to above:
https://www.facebook.com/developers/apps.php
shows a separate API Key and Application ID.
BUT this one says that the API Key and Application ID are the same:
https://developers.facebook.com/apps/
No wonder we are confused.
Yeah, but why are people going to the second one at all?
SFC itself has the link to the first one in the setup instructions and in the Help dropdown itself. Nobody should be going to https://developers.facebook.com/apps/ when SFC explicitly tells you to go to https://www.facebook.com/developers/apps.php.
Well, here’s why I did – I only tried this plugin because I am having an issue with the “Facebook Page Publish” plugin. The instructions for that send you to the site with the incorrect info (which doesn’t matter because that plugin does not use the API Key). Also, if you search google for “Facebook Developer” the site with the incorrect info comes up first.
Is there a way to make this plugin automatically publish posts only from certain categories? That is why I like Facebook Page Publish…
Thanks!
Actually, when you search google for “Facebook Developer” the site with the incorrect info is the ONLY one from Facebook that comes up… what’s up with that? 🙂
Version 1.0 of the plugin will no longer require the API key at all.
Otto,
Your plugin looks like exactly what I need! But referring to this comment
Yeah, but why are people going to the second one at all?
SFC itself has the link to the first one in the setup instructions and in the Help dropdown itself. Nobody should be going to https://developers.facebook.com/apps/ when SFC explicitly tells you to go to https://www.facebook.com/developers/apps.php.
It looks like Facebook is redirecting https://www.facebook.com/developers/apps.php over to https://developers.facebook.com/apps/.
So even when you follow the link in the plugin, there’s no way to get the seperate API key. Is there a quick way to fix this?
Nevermind, if anyone else has this problem make sure you have version 1.0 🙂
Is there any way to recover the old API key?
I’ve updated my SFC installation, but, now my registration form looks all wrong. And I wanted it back the way it was. With autofill in the same style as the wordpress registration was.
Otto, can I preserve the SFC registration style with the new 1.0 version?
No, sorry. And going back to version 0.25 won’t help you either. Old versions of SFC will likely stop working October 1st, when FB mandates OAuth 2.0.
I’m cuurently using a plugin to modify the registration fields, so that the username is equal to the email address (look at: http://londerzeel.vantveer.be/wp-login.php?action=register )
Is there any way the plugins can be compatible?
The site is in development, and i was realy happy the way the integration was :p