cherlihy,
Here is the story of your issue:
1. [2012] Since first version of the plugin came out Facebook API allowed you to set/change title, description and the image of the shared link.
—- SNAP passed description and the image to each API request to share a link.
2. [July 18, 2017] Facebook made a description to stop allowing you to set/change title, description and the image of the shared link. They said they done it to “fight fake news”.
—- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.More info about that: https://www.nextscripts.com/known-issues/facebook-shared-links-info/
3. [July – November 2017] Many big Facebook’s partners complained about their decision.
—- SNAP was still passing description and the image to each API request to share a link, but those parameters were completely ignored by Facebook.
4. [November 07, 2017] Facebook decided to partially rollback it’s decision about disallowing an ability set/change link info. They decided to allow that to some “selected partners”.
Facebook releases API v2.11. That API comes with one change affecting SNAP. Those “Selected partners” (officially called “owners of the URL”) are now able to set/change title, description and the image of the shared link. Everybody else is now getting “(#100) Only owners of the URL have the ability to specify the picture, name, thumbnail or description params” errors.
—- SNAP was still passing description and the image to each API request to share a link, but those parameters were NOT IGNORED anymore. They were the cause of the (#100) error.
5. [November 10, 2017] We release SNAP 4.0.11. We completely removed the part of the code that were passing description and the image to each API request to share a link. SNAP is no longer passing this parameters and that has fixed the (#100) error..
SNAP is open source plugin, you can take a look the code and see by yourself that part that were sending “picture, name, thumbnail or description params” were removed from the fb.api.php file. All you need to do to fix your issue is update your plugin to 4.0.11. It’s physically not possible to get this error in 4.0.11. If you are still getting the error, your plugin is not 4.0.11. Our support has told you that about 30 times. Please update your plugin. Make sure all they files are updated. Clean all the cache. Once you get the update it will work. This issue has affected a lot of people between November 7 and November 10. 4.0.11 fixed it for everyone.