Databases
StackOverflow2013
Postsdbo
POUnable to Administrate Facebook Comments Plugin
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to Administrate Facebook Comments Plugin
    text
    copied!<p>Everything seems to be correctly setup except I am not getting any administrative options. I have the Social Comments Plugin working, I even have the Open Graph tags properly setup and tested using <a href="https://developers.facebook.com/tools/debug" rel="nofollow">https://developers.facebook.com/tools/debug</a> (Response Code:206) it does scream errors; except still no administrative options.</p> <pre><code>&lt;meta property="og:type" content=""&gt; &lt;meta property="og:title" content=""&gt; &lt;meta property="og:description" content=""&gt; &lt;meta property="og:video" content=""&gt; &lt;meta property="og:image" content=""&gt; &lt;meta property="og:url" content=""&gt; &lt;meta property="fb:admins" content=""&gt; &lt;meta property="fb:app_id" content=""&gt; </code></pre> <p>This is the meta tags I am using. They are all correctly implemented and tested. I tried with <code>fb:admins</code> and <code>fb:app_id</code> on there own and together. I also have my Facebook User ID and APP ID correct as well. Still no admin features.</p> <p>The code I am using to make the plugin work is based on exactly what is displayed here. It comments plugin is working. So I am assuming it should all unfold.</p> <p><a href="https://developers.facebook.com/docs/reference/plugins/comments/" rel="nofollow">https://developers.facebook.com/docs/reference/plugins/comments/</a></p> <p>Something I am missing or is this feature not available for the comments plugin?</p> <p><strong>Update</strong><br> I just did another test and added a bogus User ID and the debug did not display an error and excepted the fake ID. Shouldn't it have caught that?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload