Sharing URL On Facebook using Addthis - facebook

we have a news website and using AddThis plugin to share news on Facebook ,
sometimes when we try to share news on Facebook it doesn't detect the page info (title ,desc , image ) and when we put the same URL on Facebook debugger every thing running correctly and
page info detected , and when return to the web site and use the same URL we can share it normally .
the web site created using asp.net 4.0 + SQL server 2008 + iis 6 and the website behind a firewall
thanks
===
( Update )..
after trying Facebook debugger i got this error :
"Error Parsing URL: Error parsing input URL, no data was scraped. "
and after trying it after 2 days i can share the link without use the debugger .
then i try the debugger and it's working with out error (same link )

Facebook uses a lot of caching especially for shared links. Once a user has shared a link, Facebook will cache the title, test and images it scraped from that URL.
When you pass a URL though the Facebook Debugger, Facebook will clear it's cache on that URL and use the new data. So the actual act of passing the URL though the debugger is what is causing the differences.
Usually you'll only pass the URL though the debugger again when something has changed on that URL and you want it Facebook to know about it.

The Facebook URL debugger also serves to re-scrape the page, so if you're having trouble with sharing the wrong data to Facebook run it through there to refresh their caches.

Related

400 error displayed when sharing page to facebook

When sharing page to Facebook from website the facebook share window reports that the page url is returning a 400 error and is not shareable. In contrast the Facebook debugger tool reports that the page is OK after rescraping.
I am expecting that since the url is displayed when requested, that sharing to Facebook would not be an issue.
Wondering if anyone has experienced this issue before and if so what was done to resolve the issue
Further details:
When using the facebook debugger tool and rescraping the page url it is reported that the page is OK. Regardless of the number of times that the page is scraped using the debugging tool subsequent shares to facebook from the site page fail with the same error.
Affected web page

Failed to get composer template data. blacklisted?

URLs to our app https://makesense.org doesn't display nice on facebook anymore ( ex: https://beta.makesense.org/challenges/763 )
The Open Graph Object Debugger show an "Failed to get composer template data." error.
I updated all our API calls to Graph 2.0 but the problem is still there.
I also read on this thread that I could come from our CDN ( s3 bucket ) that is blacklisted. So I copied the bucket form makesense-production to makesense but it is still not working.
Facebook does scrap and update our make-sense:challenge objects, it is just refusing to display the content...
Here is an example of scraped but not displayed page https://beta.makesense.org/challenges/763 that has https://graph.facebook.com/887885094602305 for facebook object.
I wonder if facebook did blacklisted our website.
Does anyone knows how to fix this issue or to contact facebook support ?

The facebook debugger is giving 500 error

The facebook debugger is giving 500 error for your webpage. It is unable to get my og metatags values. However, og metatags are present in the web page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fstaging.eco.ca%2Fcommunity%2Fblog%2F5-fascinating-green-jobs-youve-never-heard-of%2F68170%2F
Take a look at your IIS configuration. Something in there is refusing connections from anything that isn't a web browser.
Your page returns a 500 error for the W3C validator also.
For me it was because when Facebook, Google or other robots access the page, they don't send a language like a browser does, and in the code we were using the browser language to determine the content language.
I want to share my experience about this facebook debugger 500 error. I was getting this error without any explanation on facebook debugger. I checked my server side and domain records, tried what I found on internet with no luck. It took me long time to discover the problem.
Problem was I was sharing url within a restricted area in my website while sharing for first time. Let me explain, I have a test page in my cms, before I publish anything, I test if everything's ok. I realised whenever I test a content, facebook tries to crawl site, but it's in a restricted area. So I moved anything about facebook from my test page.

Feed dialog to event/fan page says "Sorry, something went wrong." after clicking share

Having some issues with the feed dialog when attempting to post to a event or fan page. In my application I am using the JS API and FB.ui using the method feed.
But for a demonstration you can do it using the feed url too for example:
http://www.facebook.com/dialog/feed?app_id=131727613511269&to=287203454659917&redirect_uri=http://www.timeanddate.com/
After clicking share you get the:
Sorry, something went wrong.
We're working on getting this fixed as soon as we can.
Where:
app_id = your app
to = a event / fan page
redirect_uri = a url you are allowed to redirect to
note that the app has publish_stream permissions. (it also has manage_pages for fan pages)
The app in question by the way is: http://apps.facebook.com/tndcountdown/
Thanks,
Andy
EDIT:
An Example taken straight from the documentation:
http://www.facebook.com/dialog/feed?app_id=123050457758183&link=http://developers.facebook.com/docs/reference/dialogs/&picture=http://fbrell.com/f8.jpg&name=Facebook%20Dialogs&caption=Reference%20Documentation&description=Using%20Dialogs%20to%20interact%20with%20users.&message=Facebook%20Dialogs%20are%20so%20easy!&redirect_uri=http://www.example.com/response&to=287203454659917
just replace to=287203454659917 with an event.. (make a test one like it did there)
A few issues I've run into will dialog is that Facebook tries to fill in any missing data. So if you don't provide a description and caption, Facebook will try to scrape the page to get that content. Depending on how the page responds to the "scraping" Facebook will error out. I always make sure I include at least a space for those fields.
It seems the feed url you provided is similar to what is in the documentation. But the demo in the documentation has extra parameters.
I'm about to add page support to my Facebook app, which does the same thing as yours.
http://apps.facebook.com/countdown-timer/
As I posted here - Facebook Send Button - 'Sorry, something went wrong.'...
I had the same problem & worked out that this was due to linking to a Facebook page that did not have a vanity URL set up (i.e. http://www.facebook.com/CubicMushroom rather than http://www.facebook.com/profile.php?id=261963707177053). If you set up a vanity URL for the page it seems to work OK (providing you link to the vanity URL version of the page URL).
To claim a vanity URL, once you have a certain no of like (it used to be 25, but think it's a little lower now) visit https://www.facebook.com/username/

Facebook Share button returning error

Example url:
http://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Fwww.rugbydump.com%2F2011%2F09%2F2124%2Frugby-world-cup-daily-tonga-beat-japan&src=sp
That's what's generated by the Share JS. If you visit the link (after decoding):
[...].com/2011/09/2124/rugby-world-cup-daily-tonga-beat-japan
You can view source and see open graph meta tags.
If the share url is changed to:
[...].com%2F2011%2F09%2F2124%2Frugby-world-cup-daily-tonga-beat-japan2&src=sp
(Adding a 2 to the end of the url) the result is fine. Likewise with other posts:
http://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Fwww.rugbydump.com%2F2011%2F09%2F2119%2Frugby-world-cup-daily-christchurch-revisted&src=sp
So all I'm getting is "Error" with no way of knowing what went wrong.
Any insight would be great. A thought was that the url was flagged or banned by FB but no way to tell.
[...] is used cause I can't use more than 2 urls.
I re-linted your URL in the Facebook developer debug page:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.rugbydump.com%2F2011%2F09%2F2124%2Frugby-world-cup-daily-tonga-beat-japan%2F
and it appears to work fine now. Facebook caches the data obtained from a page, so it's likely they hit your page during a period in which it had an error message instead of the usual contents.