3

You should start debugging with your server logs i.e. check if they contain any clues as to what happened when the crawler was requesting a given resource. A sample log line would look like this: 834:2a03:2880:ff:16::face:b00c - - [12/Jan/2019:18:17:31 +0100] "GET /wp-content/uploads/2018/11/alpha.jpg HTTP/1.0" 200 534066 "-" "facebookexternalhit/1.1 (+http:...


3

There are multiple methods for dealing with unwanted comments, and all of the methods are what Facebook calls "moderation." You must configure some things on your Facebook App page and on your webpage so that you can use the various tools. I would start with the FAQ section on this Facebook Developers page, and find the combination of tools that you like ...


3

Ultimately this type of metadata is never going to be part of the W3C spec and is therfore never going to be seen as valid by any validation engine. I've used name instead of property before. Facebook's validator throws a warning but still parses the data and the page then passes a w3c validation.


2

It's still not doable via facebook. You can send sound files via message, and they can be played in the messages. Facebook doesn't have an option to put up only audio files. You have to turn your MP3 file into a video file then add a picture so it can play or use some external service for this. For example, if you upload your file to https://clyp.it/ you ...


2

It's not needed, but it can be useful. The important bit in defining the use of og:title is "as it should appear within the graph." In general, you want that to be the title of your blog post(or whatever). If your site's HTML titles are just that, then there's no real difference here. On the other hand, many sites produce title tags that look like some ...


2

**You need to create a 301 permanent redirect from http to your https in your .htaccess file. (This method will update most social sites IE Google +1) RewriteEngine On RewriteCond %{HTTPS} !^on$ RewriteRule (.*) https://yourdomain/$1 [R,L] EDIT: This method will regain FB likes and shares. You can refresh it with FB debugger


1

Our issue was with newly installed SSL certificate. Our blog is also hosted on WPEngine and in our case the problem started to appear after we updated our SSL certificates. It took me a lot of convincing and elevating the problem until WPEngine support began to dig deeper until they found that they forgot to chain the SSL certificate. Facebook didn't ...


1

One workaround I have found which seems to work most of the time is to take the image which has been edited in Photoshop to a pixel size of 1920x1080 and exported (at 100% quality), and to open it in another image editor (Fireworks) and export it from there (at 90% quality). However, the above procedure did not work with one particular image. For that image,...


1

Your code fired surely this error: Share App ID Missing. fb:app_id is a required parameter, missing of it could cause further error / misinterpretations. Try to add fb:app_id and fb:admin - i guess after this you will get rid of the error you describe.


1

192.168.56.101 is a local IP, I can't access it, and neither can Facebook.


1

Actually, there are a few ways to do this. It's just not as simple as simply embedding the Facebook social plugin. You can use the social graph API to fetch the last 500 fans to like a page. You can also gradually scrape the data by repeatedly refreshing the social plugin and recording unique user IDs. You can also use Facebook's JavaScript SDK to ...


1

Using the Social Plugin - Like Button you can't tell it to like a direct facebook object (update, comment etc.) For this you will need to use the Facebook Graph API for Posts. Furthermore, you would need to create an new Facebook Application, visitors then would need to accept your applications permissions to their facebook profile and then programatically ...


1

Are we allowed to import these comments for display on our site? Technically speaking (and if I understand your issue well), those comments are not generated on your platform in the first place, so they cannot be covered by some kind of agreement between the user who created them and you. It is more like you are willing to import something your don't own ...


1

This issue comes from using gzip in my page. When I disable gzip, Facebook is able to scrape information from my pages. See: Response code 200 but nothing is scraped by the Object Debugger


1

I guess you would be liable for a copyright suite from FB since the photos do not belong to you per se. I guess you could put in some sort of a T&C if its a login based site to work around this (meaning shifting the liability to the user which is a common practice these days).


Only top voted, non community-wiki answers of a minimum length are eligible