I installed drupal 7.26, clean install, only module filter and fblikebutton 7.2.3 installed
In the block or content area, or own block nothing shows up however i set the proper permissions.
The area is there and it's empty. This is the code that show up:
<iframe scrolling="no" frameborder="0" allowtransparency="true" style="border: none; overflow: hidden; width: 450px; height: 80px; " src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Flocalhost%3A8888%2Fw%2Fnode%2F3&layout=standard&show_faces=true&width=450&font=arial&height=80&action=like&colorscheme=dark&locale=en_US&send=false">
<!DOCTYPE html>
<html id="facebook" class="no_js" lang="en">
</iframe>
Comments
Comment #1
bsandor commentedComment #2
anne1960 commentedNeither the share or the like buttons show. I use a lot of views in my site
Comment #3
hackerlib commentedI'm having the same problem after upgrading to drupal core 7.26. The static like button does not show up on my website anymore.
This is the code that shows up when I view the page source:
<iframe src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Fabi.localhost%3A8082&layout=button_count&show_faces=false&width=80&font=arial&height=25&action=like&colorscheme=light&locale=en_US&send=false" scrolling="no" frameborder="0" style="border: none; overflow: hidden; width: 80px; height: 25px; " allowTransparency="true"></iframe>If I follow the link in the code I see the button in its own browser window, but nothing shows up on the page of my website.
EDIT: I now realize the problem was caused by Ad Block Plus being enabled for this site. Once I disabled Ad Block Plus the button showed up fine.
Comment #4
kopeboyI'm having the same problem with the Dynamic FB like button.
I (as admin) can see it, but others can't.
I chose to show on Content Area, and placed it in manage display.
I am using Display Suite, FB connect oauth.
EDIT: I'm stupid, didn't have the permissions. Advice: tell on your module page to configure the permission to see the button, or make it default!
Comment #5
gvsoI couldn't reproduce this issue.
What @kopeboy pointed seems to be due to permission configuration, which was now added in the project page.