I've been using facebook.com/sharer/sharer.php to redirect users to facebook with a pre filled message using the parameter quote but it doesn't seem to work anymore.
We can still go to facebook to share a link but the message is not pre filled anymore. It still worked a while ago, did Facebook (Meta ?) changed anything recently ?
Thanks in advance.
https://developers.facebook.com/support/bugs/734680371318112/:
I got an update from the product team, the quote feature has been deprecated, we will update the document to reflect the change.
Bruce
So this has been removed, only the documentation has not been updated to reflect this yet.
Related
I am having this link:
http://www.myqourse.com/offer/557/en/Certificate+Business+Professional+-+CBP+Leading+through+change
when I post it on WhatsApp, the link renders perfectly. However, Facebook tries to fetch http://www.myqourse.com/www.myqourse.com/offer/557/en/Certificate+Business+Professional+-+CBP+Leading+through+change
Any thoughts why is this is happening?
Solved it! I had a pretender.io middleware, that, was not compatible to my new htaccess. I updated the htaccess and removed pretender.io and forgot to do that to my middleware!
Hi guys I appreciate your support.
While investigating the issue, i figured out that i used to use prerender.io before, though i removed the code from my project, it appears i forgot to upload updated Kernel.php (and remove prerender.io from global middleware), now things works perfectly!
I have an issue with ALL facebook comment plugins out there... We use Joomla 3.
While having such a plugin enabled, facebook fetch the article BEFORE publishing date (which always is set in the future on the site), with the result of a 404 error.
Upon publishing facebook doesn't refetch the article when our reader tries to share it on facebook, resulting in 404 error message on facebook, even though the article is live and published.
If I go to the facebook debugger, and refetch, it works alright - but we can't do that with all articles every day.
Is there a way to restrict a plugin to be executed either if the article isn't published, or to a certain user group?
My suspicion is that this occurs if an editor checks his article before it is published, so if I can restrict the plugin for special user groups it could maybe work..?
Appreciate any ideas...
With kind regards,
- Johan.
Open the main PHP file in the plugin, and then, in the beginning of the function onContentBeforeDisplay add the following code:
if ($article->state != 1)
return '';
Do the same thing for the function onContentAfterDisplay.
The 'page_id' field in the checkin FQL table. Please use 'target_id' instead.
I understand what it means, but I don't know what I have to meet the requirements of this ('page_id' -> 'target_id'). I was searching in my code and I can find directly query to this field. I looked to Facebook SDK as well, but I cound't find it neither. I'm search for HTML, javascript, but I still can't find it.
I used in my app retriving user datas in scope - email,user_likes,publish_stream and checking if user like specified page.
Maybe someone know what has to be changed?
I am facing the same issue to all of my apps. I am not using FQL at all. As I get it it's just a notice and if you update your app details you wont have a problem. Just tick the July 2013 option and you are OK.
If anyone has a different solution please write it here.
Hello fellow community members,
I was unable to find a helpful answer, so I will give this a try: I recently developed a website that has a FB "Recommend" (same as "Like") button implemented. I have never dealt with this before, hence my complete lack of knowledge.
Now, I implemented the code the FB developer's Like page (--> http://developers.facebook.com/docs/reference/plugins/like/) creates correctly into the website (both the script and the DIV-tag, yet something that is not automatically generated seems to be missing and needs to be added for the button to work correctly. It currently does not post to the FB wall.
Upon doing a debugging check, I received the following results: [...]
Unfortunately, I have no clue what to do with that data. How and where exactly in the HTML code do I implement those missing TAGS and PROPERTIES? Any help would be highly appreciated...
Kind regards & many thanks in advance, :-)
Doc
It looks like you're missing the Open Graph meta tags. Those go into the head of your page.
Facebook has a generator to help you create the tags, but you'll need to add them into your markup.
This question is similar to: Facebook Error 191 on canvas app using FB.ui() for the 'feed' dialog (worked before, stopped working last week) which was never answered.
Starting today, after the user likes the page and enters the contest, the share dialog which presented itself stopped working and gave:
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.
when logged in as an admin and just an error occurred for other users. This tab has been running well for a while now. I have confirmed it with an associate of mine. They did make a change to another part of the app (yesterday and today) but the sharing was still working until this afternoon. They did not change the part that generates the dialog.
The tab is: https://www.facebook.com/MedjoolDates/app_355398587864294
Anyone have any insight? Feel free to use 'cancel' rather than sharing and fake data to sign up, then unlike the page if you wish.
Thanks in advance.
David
Same problem here, there is a bug posted on Facebook Developes here:
https://developers.facebook.com/bugs/273845842724431
Can't help much without seeing your code.
One thing to check, make sure your redirection_uri is exactly as your domain registered with FB and that you include a trailing / ie http://www.myurl.com/ rather than http://www.myurl.com
I can't answer why it changed, but I had that error fixed by the above change before.
I am having the same issue. Am developing a new app with FB.ui feed functionality, which worked OK yesterday and today it gives the same error as OP.
Went back and checked an > 1 year old app with the same functionality; same error. I cannot see any other solution, than the FB dev team has changed something and not given notice.