Hi @mail4cindi,
Recent privacy policy changes from Facebook, regarding what FB will now allow across their API, is the culprit here. If the FB users that have shared their posts have privacy settings enabled, while the post will come across within FB, Facebook does not allow ANY private content out through their API.
Again, this is fairly recent, and FB isn’t particularly forthcoming about what they will allow & not allow. Mainly, if the root post (or attached post) is coming from a FB user with privacy settings enabled (or specifically set to share with a small group), FB will no longer allow that post across their API (which 3rd party plugins like our FTS plugin use to access FB content, but it is FB who ultimately makes the rules). We used to be able to display any public account image, but that changed in April 2018. In the wake of the FB / Cambridge Analytica scandal, FB has clamped down then and introduced more privacy protocols periodically since.
Unfortunately, there is no fix for this (unless FB reverses this some day). You can just make sure that all of your FB Page’s privacy settings are set to public, specifically that there are no age or country restrictions enabled.
Best regards
Hi,
Thanks for taking some time to provide some feedback. I’ve double-checked the FB Page settings and nothing is set to private concerning posts, friends, following, or listings. Everything is set to Public, including the posts themselves. If it’s not that, what else could it be? Do I have to tell my client that this simply won’t work and that we should delete the plugin because it’s Facebook’s fault? They don’t want it to show with these errors.
Hi @mail4cindi,
Typically this error will show up if the FB Business Page is sharing a post from the owner or admin’s personal FB page. It did not used to be this way, those posts used to display. If the FB Business Page can post that content directly (instead of posting the shared post), that would be the workaround.
These are new Facebook rules with regards to FB’s API. At the moment, there isn’t anything we can do. Obviously, no one would want error messages showing on their site. Our developers have reached out to FB’s developers to find a solution.
