Facebook Comment Mirroring doesn't work part of the time - facebook

EDIT: This has been confirmed as a bug by Facebook. You can follow its' progress here: https://developers.facebook.com/bugs/1624076297911442/
We have set up Facebook Comment mirroring and it isn't mirroring the comments from Facebook to our website all the time. The URLs are posted utilizing the exact same tactics (no extra slash, no www, etc.). The URL that is loaded in the DOM on the page is the same exact URL that is posted on Facebook.
Here is an example of an article not working:
FB: https://www.facebook.com/djboothnet/posts/10153619844952006
URL: http://djbooth.net/news/entry/2015-05-23-eminem-childhood-home-bricks
Here is an example of an article working:
FB: https://www.facebook.com/djboothnet/posts/10153621575602006
URL: http://djbooth.net/news/entry/2016-05-24-oprah-paul-mccartney-kanye-west-block
These ARE new web pages that were created after we enabled the setting. Look at the posted date on the entries. There are entries older than that Eminem one that have comment mirroring working.
Example:
http://djbooth.net/news/entry/2016-05-23-biggie-grape-juice-big-poppa-lyrics
https://www.facebook.com/djboothnet/posts/10153619528772006

Comment mirroring only works for new URLs, that you added the comments plugin to for the first time after comment mirroring was enabled.
There is no way to activate it for older URLs, that have already been commented on before.

I have also noticed that not all posts has a comments mirroring. You can ensure and get more information from the Facebook API about if posts has comments_mirroring_domain filled with proper domain.
Please follow the checklist: https://stackoverflow.com/a/40578720/1815881
Notice, that From 6th Feb 2018 Facebook comments mirroring is deprecated and no longer supported.
Comment Mirroring: Pages that currently have Comment Mirroring enabled
will continue to mirror comments for the next 90 days. Full
deprecation of Comment Mirroring will conclude on 2/6/2018. Comment
Mirroring is no longer available for Pages that do not have it enabled
already.
https://developers.facebook.com/blog/post/2017/11/07/changes-developer-offerings/

Related

Facebook posted link crawl

Here's a problem: I've got some number of links posted to groups "as is". That posts look like a link, nothing more. Is there a way to make that links crawled to previews, as Facebook automatically does when we share a link or post it with a minor delay? Without re-posting them.
I've had that with slow internet connections or weak devices.
Or you can read this: http://www.robblatt.com/technology/facebook-previews-not-working-heres-a-fix/
Anyhow, if it doesn't show the preview at any try, you should - before trying again - refresh the page, as (mentioned in above link) if it doesn't go the first time, it never will, unless you refresh.
otherwise, did you update the page recently (or was it recently updated)?
Edit: try adding this to the end of the link: ?=1

Facebook no longer picking up *any* meta data from my WP blog

I've been running a blog for years now, and sharing blog posts (with the correct thumbnail, title and description) on Facebook always worked fine. Last week however, when sharing new blog posts, all the meta data was obviously missing - Facebook didn't even pick up the title of the page. When debugging the new blog posts, I get:
Response Code : 503
Missing Required Property: The og:url property is required, but not present.
Missing Required Property: The og:type property is required, but not present.
Missing Required Property: The og:title property is required, but not present.
-for http://www.discodemons.net/2012/02/16/moullinex-peaches-maniac/
When debugging old posts (and by old I mean posts published before that day when Facebook suddenly decided to stop reading meta data from my site), everything's there, I can share the link with picture, thumbnail and description.
There are two things troubling me:
1) I have all important meta tags explicitly specified in my header and my functions.php - when viewing the source code for the blog posts (see for yourself here: http://www.discodemons.net/2012/02/16/moullinex-peaches-maniac/
) , everything's there. I didn't change anything on my blog for weeks (or maybe months), and yet, from one day to another, I can't share my links on Facebook correctly anymore - even though all the required meta data is there.
2) Facebook is able to pull title, image etc. from even the most simple sites, that don't have any meta data included. I've tried and removed all the meta data from the header and functions.php, and yet facebook couldn't pull any information from my site?!
I've tried disabling all comments, tested some WP plugins that put the correct meta data in your source code, disabled them again, even removed all FB-related plugins such as like/sharing button etc. Any help on this much appreciated, I haven't got a clue how I could possibly fix this!
It seems as though your WP server is returning a 503 server error for all scrapes from Facebook. It may be that this is a security feature you enabled recently, or a plugin that attempts to serve different content to Facebook for the purposes of scraping.

How do I make Facebook comments public for all on my website?

I've added facebook comments to my website using the following steps:
I created a new app herehttps://developers.facebook.com/apps/
In the auth dialog page for the app, I set 'default activity privacy' to 'Public'
I got the code for the comments box here https://developers.facebook.com/docs/reference/plugins/comments/
I used the HTML5 version of the code and added it to my site in the two places specified - right after the body tag and where I want the comments to appear.
I then opened the comments moderation tool for my new app.
https://developers.facebook.com/tools/comments?view=recent_comments
I clicked on 'Settings' and turned on 'Make every post public by default'
I also listed myself as a moderator.
I also added
<meta property="fb:app_id" content="{YOUR_APPLICATION_ID}">
inside the head tags for the page.
When I go to my site - the comments box appears to work ok. I can make a comment, but I can only see comments made by me. I cannot see comments made by people I am not friends with. How do I fix this problem? I'd appreciate any help.
Thanks
Every comment you leave on a facebook-comments driven web site is public, the same way it is on a fan page. Even a non facebook member can leave a comment.
I am looking for a way to turn it off and get the same permissions you have on your facebook wall. Currently, everybody who has the link can see the page content and all previous comments.
Had the same issue and figured out that Facebook grabs urls differently for displaying and submiting comments.
If the url you're providing him in data-href (e.g. short url) is different than the window.location url (url in address bar), then it's probably the case.
P.S. I know that the question is from 2011, but someone else may show up with the same problem.

Facebook comments box with comments from multiple urls

I am looking at replacing the comments on my news site with a facebook comments box. This would mean that every time someone posts a news article people can comment on it. This would require many comment boxes for many urls.
On the front page of my site however, I have a feed to all the comments that are posted all over the page. This makes is useful for people to see the discussion happening around the site.
Is there a way to show all the comments that are being posted on my site in one location if I move to facebook comments?
Essentially it would be a feed of all the comments from the different urls.
For each url you have, you would need to occasionaly pull the comments down using the Facebook Graph Comments API with a URL like: https://graph.facebook.com/comments/?ids=http://developers.facebook.com/docs/reference/plugins/comments. You would then need to build something to display this. There are no social plugins built for this.

Why is Facebook returning the wrong page (affects Facebook Like and Share URL)?

When we first put up a blog post, Facebook often (but not always) gets confused about what the page is. Specifically, if you try to use the Like button on the blog page OR if you try to share via the Share link on your profile, Facebook will see the root blog page rather than the actual post page.
For example, we recently posted:
http://thisorthat.com/blog/2010-song-of-the-year-round-1-results
If the user "likes" it, it returns the title for:
"http://thisorthat.com/blog"
When you run the post URL through the FB Linter, you can see the problem.
"http://developers.facebook.com/tools/linter?url=http://thisorthat.com/blog/2010-song-of-the-year-round-1-results"
In the Debug section it shows an extra og:title, og:url, description and og:image (the last 4 rows of the Debug section). This is the meta data from the root directory. What we cannot figure out is why. Why is Facebook seeing the correct meta data on the page and then also pulling the meta data from the root directory (and using that incorrectly to populate the data for the Like button and the Share URL tool)?
One other oddity. FB "figures it out" after a few days. Of course, by that time relatively few people are viewing the post.
UPDATE -- I want to thank Peter Bailey again for his answer, but we also discovered that there was another issue that we had to resolve before the Like button worked.
The issue was that we were displaying the Facebook the Like button on a post that was not yet published. The problem with this is that FB then can't resolve the URL and "guesses" as to the correct URL. In our case, it always guesses thisorthat.com/blog. Unfortunately, it then caches that guess for a number of days and that cache cannot be cleared by the Linter. So the ultimate solution was to both fix the og:type as Peter suggested, but also to remove the Like button from the blog post preview. It's very important that you don't show FB a page before it's published or if you do, change the URL.
Pretty sure it's your Open Graph type that's the problem.
<meta content="website" property="og:type"/>
Per the documentation
Use article for any URL that
represents transient content - such as
a news article, blog post, photo,
video, etc. Do not use website for
this purpose. website and blog are
designed to represent an entire site,
an og:type tag with types website or
blog should usually only appear on the
root of a domain.