Thread Starter
gxxaxx
(@gxxaxx)
The FB Object Debugger was complaining that I had two app_id
Investigating I noted that Facebook Comments plugin was adding the following:
<meta content=”xxxxxxxxxxxxxxx” property=”fb:app_id”>
with the correct id (not the xxx)
But, Like & Send plugin adds the following lines to the header:
<meta content=”” property=”fb:app_id”>
<meta content=”” property=”fb:admins”>
Disabling the Like & Send will remove those lines from the header.
However, that does not fix the missing comments, they are still missing.
Thread Starter
gxxaxx
(@gxxaxx)
On the support page: http://peadig.com/wordpress-plugins/facebook-comments/ the following code is indicated as being inserted into the document:
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=YOUR_APP_ID";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>ent.getElementById('fb-root').appendChild(e);
}());
</script>
The actual code inserted on my site is:
<script>
(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/sdk.js#xfbml=1&appId=145483842240169&version=v2.3";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));
</script>
Seems like the extra </script> is a mistake in the support page.
However, the missing ent.getElementById(‘fb-root’).appendChild(e); looks like a good candidate for causing my comment section to be missing.
Is this the deal? Or, perhaps there is something else entirely going on?
In any case, I have exhausted the semi-useful poking and prodding I’m able to do.
Hopefully better minds than I will have a clue.
Hello,
We are having issues with our plugin all the sudden not working. I pinned it down to Nov. 5th.
We lost our ability to moderate comments.
I exhausted all possibilities of it being another plugin–or our template working against it.
Thread Starter
gxxaxx
(@gxxaxx)
I just discovered that our plugin is working in Chrome but not Firefox. Will check on a few installations to see if this holds true on other computers.
Ours is not working in Chrome or Firefox.
