I integrated Facebook Comments plugin on my web page. I followed Facebook directioons described here https://developers.facebook.com/docs/plugins/comments
For several years everything worked fine, but some two years ago the comments are not visible in Firefox, Opera, Edge, IE. In Chrome everything is fine. This is my testing page: http://kacka.baldsoft.com/test.php
What should I do to display Facebook comments in all browsers?
Related
I have a facebook app built using iframe. It works ok on most modern browsers except Safari on Windows platform. On Safari windows platform, the cookies seem to get lost as a user move from initial form page to 2nd page with questions.
Here is the live link
http://on.fb.me/1hCfgOX
Can someone help me on how to fix this?
Ok, i found a fix for it which works perfectly. Checkout the following links:
Safari 3rd party cookie iframe trick no longer working?
Facebook Iframe App with multiple pages in Safari Session Variables not persisting
And
http://lightyearsoftware.com/2009/11/on-the-pain-of-developing-for-facebook/
I hope this will fix your issue also, as it fixed mine. If you got any problem, let me know.
Thank you
besides header, you might also need to add w3c/p3p.xml and w3c/policy.p3p files to your website. See here for more details and sample files: Session null in IFrame in ASP.net MVC only in safari browser
All the Facebook comments have disappeared from our site's webpages (see: http://www.around-around.com/wanted-13/).
I've run the pages through the Debugger, and it appears that they're ok (just warnings about descriptions, etc.).
But when I was trying to see if there was new code for the comment box from FB, I used the FB comment plugin creator—that's when something strange happened. The example site shows up just fine; our site is rendered with a .... Weird! Frustrating!
We've been using FB comments for over a year now, and they work pretty well. But this is really frustrating. Here's some proof: https://graph.facebook.com/?ids=http://www.around-around.com/wanted-12/
Have we been...um...banned?
It's a facebook comments plugin issue at the moment. Check this https://developers.facebook.com/bugs/383938611736678?browse=external_tasks_search_results_5269356c254c23e51751890
Hopefully it will be fixed soon.
I created a Facebook "Tab App" that appears to be working in Chrome, Safari and FireFox but doesn't seem to load at all in IE8 (and older).
Here is the link to the tab on Facebook:
https://www.facebook.com/lapalomaacademy/app_190322544333196
I also uploaded the code to a page outside of Facebook, and IE8 seems to load that page fine (you can also view the source code on this page):
http://lpatucson.org/facebook/nonfans.html
Any ideas what the issue could be?
I have just added in the new Facebook Recommendations Bar (using the HTML5 version) to a number of blogs and realised that some of them aren't working. After a little digging I managed to pin it down to when I also have the Facebook Comments plugin on the same site. As soon as I comment that out it all works again.
The following is being logged in my console 'FB.getLoginStatus() called before calling FB.init()'.
None of these sites have anything on the front end we have developed that that use FB.getLoginStatus.
The Facebook comments plugin already places the Facebook Javascript SDK. I am guessing you are installing the Recommendations bar along with the Javascript - which means it appears twice on the page and therefore giving you this error.
Try adding the Recommendations bar WITHOUT the Javascript - that is, put only the bit on a page that has the Facebook comments plugin. It should then work fine.
The iframe loads properly on the page tab in chrome on my computer (I'm admin of the page), but when I try to view from another FB account on same computer via Safari or Firefox, no luck.
Also, the iframe doesn't load for others.
I had the same problem. The iframe was not loading in Safari but it was loading in Firefox. And it was also loading correctly in Safari on another computer.
After about 3 hours of searching, trying and investigating, I finally found the solution.
It seemed to be a (simple) caching problem.
What I did is I cleared all website data of Safari.
Then it worked.