I'm implementing a Facebook Send dialog, by opening facebook.com/dialog/send in a popup window. When I click the 'Send' button the dialog will display the error: 'Sorry, something went wrong' – but only for certain link URLs. The best examples I have are:
Not Working:
https://www.facebook.com/dialog/send
?app_id=12345
&name=Example
&link=facebook.com/examplepage
&redirect_uri=http://www.example.com/response
Working:
https://www.facebook.com/dialog/send
?app_id=12345
&name=Example
&link=google.com
&redirect_uri=http://www.example.com/response
These links are identical except that the first one shares 'facebook.com' and the second one shares 'google.com'. Only the second one works.
The same errors occur if I use the Facebook JavaScript API with FB.ui({method: 'send'}).
Answering my own question:
Both the links now work for me, although I have not changed anything. I can only hypothesise that Facebook has either fixed this bug, or this issue occurs on some internet connections and not others.
I think Facebook is trying to read the URL and pre-populate the image and content. In your case probably because skiggle.com.au is a redirected to the other domain and facebook doesn't accept it.
Edit. Your first link works though
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/
This can also happen if you share a link to localhost
Related
I have a website that is being used by various corporate employees. Just today I have a user saying that everytime they login (even with correct username and password), they get an error saying they have to login to view the page. Basically, they type the right username/password and get forwarded to the home page, but that controller has a login required decorator which rejects them and they get sent back to the login screen. The user tried in IE10 and Google Chrome web browsers.
I have not been able to replicate this issue anywhere and unfortunately, i'm in no position to really ask this user for more information for debugging purposes :(. Has anybody seen this before??
I tried googling this, and i'm seeing issues with Django for IE but nothing with Chrome. Is there anything else that could be happening?
I'm using nginx+uwsgi on the server if that makes any difference.
Without more information this is pretty much impossible to solve.
Because no one else is having the problem and you can't reproduce it, I'm inclined to believe it's user error.
Have them clear their cache/cookies (The fact that it's multi-browser is troubling though), see if that helps.
Best guess so far without more information: The user has cookies disabled. I think Django auth relies on cookies.
How can one change the opengraph link value on a Facebook page (type: website) from
https://www.facebook.com/yourwebsite to http://www.yourwebsite.com
It seems easier than it is. I couldn't find an answer. Seems it has something to do with adding an app, and then?!
Example: http://graph.facebook.com/anguillabeachescom
I can’t see that being done anywhere on the page’s settings interface.
My guess would be you have to claim your domain with Facebook to make things work this way (and maybe have to have a special category set for your Facebook page – the example page you mentioned is of type “website”.)
I've added a facebook Like button to a few of my web site pages. All of them work except for the home page and I can't figure out why?
It is almost impossible to answer this question without seeing some sample code of your "home page".
Check your page with https://developers.facebook.com/tools/debug
If the response code isn't 200 or your meta tags don't appear properly or whatever else, at least you'll know where to look. Keep in mind that when you click like, Facebook makes a request to your page. Make sure you let Facebook do that (don't block/Redirect the Facebook crawler).
Edit: Sometimes, simply adding your URL and testing on the link above solves the problem. This is if you had a problem with the site when you first added it and meanwhile Facebook cached it as problematic. Debugging it will clear the Facebook cache for that URL.
I'm using the 'feed dialog' with my Facebook desktop appliaction to recommend my app (and not using prefilled text).
This dialog worked well before, but since Sunday after trying to post I'm redirected to an error page which requests captcha filling, and once it's done I receive an error page.
At the beginning I replaced the URI, which worked and I was able to post normally, but since yesterday Replacing the URI or the URL doesn't work anymore.
Do you have any idea what can cause this?
even i have been getting the same problem. the feed dialog directs me to a captcha and even if i enter the correct words it gives me an error that the words did not match. i was using the feed dialog to publish on my wall through an app. the legacy rest api is however working flawlessly.
I've got a Drupal website with articles on them which have Facebook like buttons.
Now I've got all the OpenGraph metatags added on the pages and it's all working perfectly except for one thing.
Site visitors can share a page URL or like a page URL.
When a new article is added and the first person who presses the like button will not see the image added in the og:image tag.
If another person afterwards presses the like button, the og:image however is visible so it seems to me Facebook needs to scrape the page first before the og:image is added in the 'Facebook Like window'.
The Facebook share doesn't seem to suffer from this problem and does it right from the first time.
Now whenever somebody adds a new article, I'd need the URL of the article to be scraped automatically by Facebook using some PHP code or some other fix...
Anyone who knows if autoscraping a URL is possible or does anyone have an idea for a workaround?
You can use the graph API with scrape=true to force Facebook to scrape you right when you create your contents
https://developers.facebook.com/docs/beta/opengraph/objects/