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.
Related
I have started to experience a really strange problem with Facebook link scraping/caching which seems random in nature.
On brand new posts when I go to check: https://developers.facebook.com/tools/debug/ with my new URL I get a message saying 'Cannot scrape: URL blocked'
We have literally been sharing URL's to Facebook for YEARS with no problem whatsoever. All open graph tags are present and working fine.
What is really weird is if I just manually press the 'scrape again' button it grabs all the bits properly and says everything is fine. It's always just the first attempt.
I have also tried manually calling the scrap API instead of letting Facebook do it when someone shares the URL for the first time and still sometimes (not always) it returns empty (just 'id' and 'url' returned) indicating the URL was blocked.
What's going on here it's driving me mad? We are nowhere near our API limits if maybe that was the issue...
Why would it say blocked first go on the debug page then literally 2 seconds later you press 'scrape again' and it works fine.
Just to note sometimes when it says blocked it still shows maybe the image in the link preview but no title or description. It's like it's grabbed some tags but then given up. Very strange...
I have checked our access logs and I can see 'Facebot' accessing our site fine.
Hope someone can help, I am really hoping this is some weird Facebook bug as I can't see any change in our code base that would effect this.
Facebook does not return anything helpful when this happens even with the API. I have no way in contacting Facebook direct either. If we are somehow getting blocked I would love to know why and fix that issue. But it's impossible to debug at the moment.
Just to note I have 3 sites all running the same code base (WordPress environment). They are all experiencing this issue. All been running fine for many years.
Cheers
This was to do with rate limiting that was not visible in the Facebook APP dashboard. Helpful...
Full details here: https://developers.facebook.com/bugs/232343637174087/
Solution for your problem: You can use Facebook image button after adding link on Facebook news feed, like shown in iamge
second thing upload image on othe site and give the image path to your website and then put it on your news feed, you can get definitely positive result using this two methods.
also refer this image
thanks hope this two will work for your problem
I have a problem on random URLs hit on Faceboook account.
After posting a note on http://www.soycarmin.com/, generated a short url with 'google url shortener' and then stick it on the wall account https://www.facebook.com/pages/Soy-CarmÃn/1394963147496673
The problem I have is that occasionally brings this url 404.
If the url income I get from goo.gl, it directs me to the site properly ''m carmine' and if I look at the fields 'open graph' these are correctly added.
This causes occasionally have to be debugged my url to share properly.
Could someone help me with this situation?
I'm creating a web app which uses Facebook feed dialog plugin in some pages. When I try to share these pages, the URLs posted to the news feed get truncated.
I'm using the direct URL approach. When the user wanna share something, she clicks in a link that is going to redirect her to the feed dialog. The link is composed as shown below:
https://www.facebook.com/dialog/feed?app_id=MY_APP_ID&link=SHARED_URL&redirect_uri=REDIRECT_URL
For example:
the URL I have in the "link":http://www.simplecity.com.br/DP/Index/?CID=0&UID=1
the URL I get in the news feed:http://www.simplecity.com.br/DP/Index/?CID=0
Has anyone already experienced this issue? Any suggestion?
The usual cause of this is forgetting to encode the link when you pass it into the Direct FB URL.
Are you forgetting to urlencode the link parameter (i'm especially thinking of the &) when creating the URL you're passing the user to?
I recently encountered the same problem with a straightforward link - I inserted:
https://example.com/page.html
into a page post. However, on the page it was rendered as:
https://example.com/page.ht...
as if the last two characters of the html extension were merely not displayed, as indicated by the elipsis. However, if you copy the link from the post you find that those chars are actually missing and the link resolves as 404. If you edit the post and reinsert the link, it is saved correctly, although the 'overflow' characters are still hidden by the elipsis. Very misleading.
What seems to work best is if you use the Facebook Developer OG tags in the page and then use Open Graph Debugger to scrape the link. This puts the URL in the FB realm and it picks up the correct link just fine. As you are doing this, the debugger tool gives you feedback to the effect: "This is the first time we have seen this URL"; which is baloney if you have put the URL on a FB page beforehand.
I have filed a bug report with Facebook; but I am not expecting them to own up to this bug.
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/
Good morning all!
I'm developing the Facebook Share button feature on a site, but i'm having the following problem:
Imagine that i have an article that i want to share with the id=1
when i shared it, by doing:
<a name="fb_share" type="icon_link" share_url="http://www.something.com/en/news.xhtml?id=1"/>
all went good.
Now, i tried to share a different article (id=2)
this took me to the article with id=1.
Is there any cache problem on the facebook side, or he caches the page http://www.something.com/en/news.xhtml and discards the request parameters?
Thanks in advance
use the following service https://developers.facebook.com/tools/debug , pass the url and facebook will flush the current cache.
This issue was mentioned on the following developer thread on FB.
http://forum.developers.facebook.net/viewtopic.php?pid=130747
Facebook share does cache pages with the same URL, but in the example you provided the URL is different, you could also try passing trough the date in the URL to make sure the page is unique. It may have been that you tried sharing that page before but the content then may have been different then ...
Mart