Hi all,
I am using fb module, it worked fine for the first time.. After configuring some changes..
when i add a application it throws me a error...
Failed to get application properties (apps) from Facebook: An unknown error occurred 1
Unable to get application properties. Possibly, you've given the wrong id or secret. Possibly, this server is unable to reach facebook's servers. Your application will not work properly!
Failed to get application properties (apps) from Facebook: An unknown error occurred 1
Failed to set the following properties for appsface application. You may need to manually editing remote settings!
Array
(
[uninstall_url] => http://www.xxxxxxxxxxx.com/fb_app/event/appsface/post_remove/
[authorize_url] => http://www.xxxxxxxxxxxxxxx.com/fb_app/event/appsface/post_authorize/
[connect_url] => http://www.xxxxxxxxxxx.com/
)
Failed to set application properties on Facebook: An unknown error occurred 1
Failed to get app properties for .: An unknown error occurred 1
Failed to get application properties (apps) from Facebook: An unknown error occurred 1
Comment | File | Size | Author |
---|---|---|---|
error-screenshot.png | 51 KB | kesav20 |
Comments
Comment #1
13rac1 CreditAttribution: 13rac1 commentedNot critical. I've experienced the same issue when FB isn't responding.
Comment #2
Dave Cohen CreditAttribution: Dave Cohen commentedI'm not sure there's a fix for this. It's a message to the administrator to say that settings were not sent to facebook automatically. You have to try again or modify properties on facebook manually, when this happens.
Comment #3
harkins_design CreditAttribution: harkins_design commentedBeen getting the same error for two days. Modifying properties on Facebook would be fine but several of the properties don't seem to be available for manual entry. Ever fix the problem Kesav20??
Comment #4
Dave Cohen CreditAttribution: Dave Cohen commenteddedisoft reported seeing
Makes me wonder if facebook has deprecated the old API in favor of not yet deprecated graph APIs. I don't understand why we don't all get that error, though. It might have to do with a migration setting.
The connect URL is the one that really needs to be set. I'm not sure whether the others are still on their form or not.
Comment #4.0
Dave Cohen CreditAttribution: Dave Cohen commentedfasdf