I have a site and wanted to share it into facebook. However, upon posting I got a notification from facebook saying:
The content you're trying to share includes a link that our security
systems detected to be unsafe:
markleobongcasan.com
Please remove this link to continue. If you think you're seeing this
by mistake, please let us know.
I checked into sucuri site check and it is 100% safe.
I checked my site using facebook debugger as what one of their support member suggested and I got this:
http://screencast.com/t/4nTfGhNd0fq2
Anybody here who has the same experience/problem? How did you fix it?
"let us know" is a link. You need to click that link and appeal to Facebook. After that, all you can do is wait.
You can also try asking in the official Facebook Developers group: https://www.facebook.com/groups/fbdevelopers/
...or you could file a bug, because it could be a bug too: https://developers.facebook.com/bugs/
Related
When I try to share this link (http://saeedreza.me/) on Facebook first it says it's an unsafe link:
It looks like a link you're sharing might be unsafe. If you can,
please remove this link:
saeedreza.me
Note: The unsafe link might be on the page you’re linking to.
I have checked this domain with Facebook Sharing Debugger and it doesn't show any error. I have also checked it with Facebook Open Graph Object Debugger and still no bug or error. It has all the proper meta tags and even the app ID.
I have also checked the link safety with different services and have received no sign of any malicious malware or suspicious script.
After passing a security check, Facebook allows to share/post the link anyways but when you try to click on the link it redirects you to a page with this message:
You followed a link on facebook.com that redirects to another website:
http://saeedreza.me/ You can now continue to this website, or go back
to the page that you were on before. Remember, only follow links from
sources that you trust.
I have also checked the site to see if it redirects to any other domain but nothing suspicious again!
I have tried to contact them so many different ways but still no luck.
Has anyone had this experience before? or do you have any suggestion how I may be able to fix it?
Try to shorten site URL with goo.gl, it's a link shim feature from FB giving you this warning: https://m.facebook.com/notes/facebook-security/link-shim-protecting-the-people-who-use-facebook-from-malicious-urls/10150492832835766/
I have tried using all different plugins (facebook, facebook comments, seo facebook comments, and more), I have even added the application manualy (https://developers.facebook.com/docs/plugins/comments/ using html5 plugin code). All options do the same thing.
Comments show up that is all fine. Readers are able to comment on the website through the box, thats fine too. But then when I want to publish to facebook, all seems good too, it will publish it. But when I go to facebook and click on the published comment, it is not possible to like or comment (on the publish comment). Facebook shows the comment on the timeline, but clicking on it gives this message:
"Object cannot be liked
Unable to like this object because it is not accessible (it may have been removed or you may no longer have permission to see it)."
I can click the link in "John Doe has commented on a link" and it will take me to the page however.
Some other strange things that happen are (on the actual wp post) when you comment and have the "post to facebook" box checked, it won't publish straight away, but give the message "This comment has not yet been published to Facebook. Publish Comment". Only after clicking publish comment will it ask permission to publish on my profile.
And then when you want to delete the message, it will say "Oops Something went wrong. We're working on getting it fixed as soon as we can." Click delete again and it deletes. No fail every time on the second time after that message.
Please help me out, before I go crazy :P Website is tryajuice.com
I am also using Yoast WordPress SEO: Social, OneAll social login, which might influence it, but deactivating them all doesn't make a difference, unfortunately.
Any help will be much appreciated.
Yesterday I received in one of my Facebook apps this message:
Tried to look for documentation about it but couldn't find it. What does it mean? I can't request READ/WRITE permissions anymore? I must do it sepparately?
As someone cited out in other question, it looks like it is not your fault and you cannot do anything about it.
Quoted from Fabrice Lefloch in what am I going to do with this Facebook alert? about the permissions
It seems that it is a mistake from Facebook developpers.
Someone has asked the same question here, and a facebook engineer answered:
The alert went out by mistake and we are working on cleaning it up. You can ignore it.
I am trying to post to user wall but I am receiving this error when when share window pops up:
The post's links must direct to the application's connect or canvas URL
Now, I made a proper Google search in hopes to find a solution, but the only one given was that I need to disable "Stream post URL security". I checked the advanced settings for my app and it is already set to disabled.
So, by having a few years of experience with development on Facebook, and by knowing how incredibly bad the communication between us developers and FB has been in the past, I'm highly doubtful that they will assist me on this. Although I have heard that feedback is better here on SO than the good old FB platform forums. Well, lets see if my only option is to set my hair on fire or that there might be a kind soul out there that can assist.
This answer from the WordPress forums via user Samuel Wood (Otto) worked for me:
Go to the Facebook App. Edit its settings. On the Advanced settings page, disable the "Stream post URL security" option.
Did you generate the access token using the Graph explorer app on FB?
Make sure you select your app from the select box on the top-right.
It will be selected as Graph Explorer by default.
This error happens as the selected app would be Graph explorer and its canvas/site url is not pointing to your site.
Doing this fixed my problem; it may fix yours as well.
With the new app interface, issue is solved by turning off the "Stream post URL security" in the "migration tab"
you always have to use the same domain for linking as specified on the app's developer settings. Now you can have several tlds, and custom prefixes as well.
For others experiencing this problem, I was able to resolve this by configuring the Facebook > App > Settings > App on Facebook > Canvas URL
Came into the office today to do some more work on my nearly completed Facebook Connect website application.
And i have discovered for some reason, the "onlogin" event of the fb:login button FBML control is no longer getting fired!!?!
To anyone else that has a Facebook Connect FBML app (and using the JavaScript API for authentication), i would advise you test your application to make sure it's still working.
A friend of mine's app (which is live) has also stopped working as of today.
What's happening is you click on the "Connect to Facebook" button, it shows the FB login dialog, you log in.
Yes, they are being logged in to Facebook correctly (thankfully), but the "onlogin" callback event is not getting fired anymore, so the page just sits there (where before the "onlogin" event would redirect to the homepage, for example).
Of course if you refresh, you are logged into Facebook.
Seriously, WTF - what have those developers at Facebook done now?!?!.
Any ideas? Has anyone read any updates/threads on this issue?
UPDATE:
8 hours and still no fix in place. I've tried to do some workarounds (there is also an onclick event of the FBML Login Button), but it's all too early in the authentication cycle.
We need to be able to hook into a post-login callback to do things like redirects, permission popups, authentication logic, etc.
Nothing we can do without Facebook fixing this.
I just hope when i come in the office tomorrow this will be 'magically' fixed, much like this issue 'magically' appeared.
Well judging by the comments here i'm not alone. It's obvious at this point that Facebook have made a change somewhere, without telling us.
I just hope they rectify this issue ASAP as there is no workaround i can see for this.
UPDATE 2
Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733
I love it how the comment from the FB guy Marc says "Only seems to be happening on old Facebook Javascript SDK", well, enable us to do server-side authentication with your Graph API (instead of just for retrieving user details/posting), and we wont have to use the old JavaScript API!
Fun and games.
FINAL UPDATE
Facebook have (seemingly) fixed this.
Let's hope it stays fixed.
Given the 'correct' answer to Anon (as he found the link).
Please confirm and vote on this bug... this should be fixed asap!!
http://bugs.developers.facebook.com/show_bug.cgi?id=11733
if in FB.getLoginStatus you are passing second parameter as true, pls make it to false.
I resolved callback issue using this trick.
Thx
This is a bug and they are about to fix it