Due to recent changes after Facebook's scandal, the Facebook source in JIG is impaired. Many of you are receiving notices that your apps should be reviewed. Let's take a look at your options.
Currently, if you use JIG with the Facebook source for a long time (especially with an old FB app), you may continue to do so without any changes. This site uses this ideal scenario, that's why all the examples are working, and that's why most users are still not affected. This is subject to change though, and we intend to bring a more solid solution to the problem (see below).
If you are new to the Facebook feature or you are having problems, your current options are:
Set your FB app up in a way that you can access your own personal profile's content
Particularly, if you received this dreader message in red when trying to add the current user: "Can't Load URL: The domain of this URL isn't included in the App's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings." There is an unintuitive solution, provided you already set up your app's domains in the basic setting...
- In your app's administration interface on Facebook, click Facebook Login on the left sidebar, under Products.
- Choose Settings as it appears.
- For the setting called Valid OAuth Redirect URIs add this URL, but replace yoursite.com with the real domain:
https://yoursite.com/wp-admin/admin-ajax.php?action=jig_fb_auth - Click Save Changes button at the bottom.
The reason you need to do this is that for new apps, the "Use Strict Mode for Redirect URIs -
Only allow redirects that use the Facebook SDK or that exactly match the Valid OAuth Redirect URIs." is toggled on and cannot be changed.
Wait for a JIG update that'll solve all of this at once
Unfortunately, this is no immediate solution, and we are aware of that. The changes didn't come with much grace period. Usually, a certain FB API version is good for at least two years with no changes to what's already working. Hence the delay as this happened too suddenly. We intend to create a single Facebook app that'll serve everyone at once. You'll connect to that, but some of the requests in this process will need to pass through us. Therefore we need to set up a service on our server. That is a big change, even if it means that it'll be easier to use the Facebook source in JIG (just one click setup for anything you wish to show). However, we need to get this one app reviewed (accepted by FB), and judging by how Instagram (also owned by Facebook) disapproves of this kind of use, and some complications might delay or even rule out this approach.
Get your app reviewed, as all notices say so. There is no user feedback that it solved anything, but it should.
With an unreviewed app, Pages cannot be accessed, even if they are your own. In a nutshell, an unreviewed app should still be able to access the pages owned by you, if you are also the owner of the app. Even with some changes to the code (using Page Access Tokens), or by even using the Graph API Explorer, this is not possible - perhaps it's a bug. Therefore, our "create your own FB app" approach is currently not applicable in any way for showing Pages' content on your site.
Possibilities of using Facebook Page source in the near future?
It's under consideration that - using one's unreviewed own app - it'll be possible to show Pages. The flow will require adding the current user first (who is the admin of the Page), then JIG'll get your managed pages and even auto-add them next to your Profile. The pages will have access via the profile you added (probably your own) - much like how alcohol and country-restricted pages required a user who can "see" that content. It'll still not allow loading any public page, just your own, but this is probably what most are after. If this method works, you can expect an update in 1-2 weeks.