i have implemented facebook facepile via XFBML on two pages. one is home page and other is signup page.
Both pages have same code on it. (using include function, so im 100% its same code) even the XFBML code is same (using include function)
if i open up home page, it shows me
Be the first of your friends to like this.
and if i open the sign up page, it shows me
Basit is using Stackoverflow
does anyone have any idea why its doing this?
i been trying anything to fix it, but its not working.. cant find any solution online eaither.
dont use data-href="url_of_the_page" in <div class="fb-facepile" data-max-rows="6" data-width="292"></div>
Related
ive been looking at a few questions over the net with no luck. I have the plugin likebox from facebook for a client who want to use that as their main source of news.
heres the website
http://114.23.32.240/~wwwturbo/manawatu-turbos/index.php/news
Its working fine however when you scroll down to the Show More button, click that it doesnt show anymore feeds it just goes to a blank page here
https://www.facebook.com/plugins/likebox/stream
is there anyway to fix this so it loads more posts? even if I can edit the code to go to their facebook page.
Thanks
I've been struggling with this for a couple of days now. I have a simple wordpress blog. I've plugged in all the OG meta tags and run the page though the debugger many times and it shows no errors.
However when people click the Like button (generated from the Like Box plugin), they get the red error message suggesting that the page be run through the debugger.
I have generated other like buttons that live on individual blog posts, and so far these seem to be working fine, its only when trying to like page there is an issue.
Also note, that the facebook page was generated from the OG meta data after I had liked it. So this isn't from creating a page in Facebook and then trying to have people like it. I mention that just in case it matters.
The other thing of note, is that if I am already logged in (just me the admin), I can like and unlike it with no errors. If however I log out of facebook, and click the like button, after entering my facebook login, I see the error just as other users have.
I've been reading forum posts for days and have yet to find a solution. My blog URL is http://www.garrinball.com
Thanks
Your http://www.garrinball.com/ parses just fine on the linter. However, this is only a small issue, you don't specify any og:image tag on http://www.garrinball.com/2011/10/christmas-card-shoot/.
What is strange is I don't see any errors. I like the christmas-card-shoot and the like button maintained my like even after page refresh.
I also logged out of facebook, went back to like it, and it prompted me for credentials as normal. I logged in, and was able to like the button. No errors.
I'm wondering if it is specific to your account you're using.
I'd suggest trying with an other fb account.
I have a fanpage tab application with a like button on it, and after a while testing I got the exact same error as you :
<!-- with the JS SDK included and inited -->
<div class="fb-like" data-href="//fanpage-url" data-send="false" data-width="100" data-show-faces="false"></div>
When refreshing, the like button is however detecting correctly the like status.
No error message shows up when using another account than my admin-dev one... maybe its an antispam function ?
I've been having trouble accessing admin privledges for the like buttons on my website (along with other things).
This is the situation:
I have made a facebook page for my website www.digitaldemocracy.org.uk
I have made a facebook app for my website that allows people with facebook accounts to register and login to the site. This works fine.
Like buttons are associated with different php dynamically created pages on my website i.e. www.digitaldemocracy.org.uk/debate/debate.php?id=3850. These Like buttons work when users click on them. I also have a like button for the main page www.digitaldemocracy.org.uk which works a bit funny as it seems to sum up all the likes from the other pages (even though they all have different URLs associated with them)
Now what I'm having issues with:
I have put 3 facebook UIDs into the metatags for admin purposes for the Like buttons. I have tested some links with the fb Linter (https://developers.facebook.com/tools/lint/) and it doesn't seem to have any issues, but when I click the like buttons myself, I get no admin features. I have also tried accessing admin priv directly from facebook, but no luck with that either.
I read that you can tie admin rights to a fb page, so then I tried it with the facebook page (page_id) for the site, but no luck with that either.
I then tried to give admin rights from my website to the facebook app, but when i test it with the linter it says that i have associate it with the specific page www.digitaldemocracy.org.uk/debate/debate.php?id=unique_id, which seems to defeat the purpose of what i'm trying to do (tie all the website pages together so i can easily administrate them).
The furthest I've got is to see the insights for the domain www.digitaldemocracy.org.uk/ (where i wasn't able to before), but I can't seem to see likes for individual pages and I don't seem to have any admin rights about publishing to user's feed or seeing who the 'likers' are! Am I missing something now?
It 'seems' to be that i'm doing all the correct things specified by the documentation, but I have getting nowhere and don't know what else to do. I have searched forums for answers, but they're just all over the place. I hope that stating my exact problem and what I've done will hopefully find someone able to help me!
Thanks in advance.
Denise
2 things I have found:
It seems the Admin link will only appear when you are using the default like button settings (ie faces on etc)
For the times that I could not get the Admin link to appear, I ran the linter and it suddenly did.
Perhaps try emptying the cache for your browser too but I have a feeling the first point might solve your problem?
I could be wrong, would love to hear someone else's opinion!
This issue has been driving me crazy ever since I accidentally discovered that these magical pages existed. I've had them show up with and without appIds in the fb js snippet. There doesn't seem to be any logic.
Item 1 from Sam Hammond doesn't seem to matter. Most of my Like buttons have data-show-faces set to false.
<div class="fb-like" data-href="http://www.mysite.com" data-send="false" data-layout="button_count" data-width="100" data-show-faces="false"></div>
From the above example I have seen the following:
Actual Web Page Like Button shows "9k"
My admin page shows "1.7k"
It's great. I can reach 1.7k people who Liked the page. But what about the rest and what about any new pages I create?
For now, when in doubt, drop the Facebook Page Like Box on your web page because at least it works consistently:
https://developers.facebook.com/docs/reference/plugins/like-box/
I also have to wonder how facebook users react when they start seeing posts in their feed from sites they Liked. It seems a bit intrusive.
I frequently use the Linter/Debugger tool on my web pages, doesn't seem to make anything appear. But this tool is highly recommended for other purposes:
updated link from above is: https://developers.facebook.com/tools/debug
I am very confused about the way the xfbml like button actually works with urls.
I had multiple xfbml facebook like buttons working perfectly fine for a couple of month on a ajax site with url with hash tag.
For example: http://example.com/#/section1/subsection1/
Very recently this stopped working and all the like buttons now only display to total amount of likes given to the root url (example.com).
I did some research and built a little testpage for this matter:
http://luckyarts.de/liketest.html
Please check my testpage to fully understand what the issue is.
The URL Linter from Facebook also didn´t really get me any further.
Any help in this matter would be highly appreciated as i am puzzled. Thanks!!
Update: I deactivated the test page... please do not follow the link. I concluded that facebook does not scrape urls of ajax websites that have an url with hashtag..so the like buttons won't work properly. At least i couldn't get it to work. Please correct me if anyone finds out otherwise. For non-ajax pages the multiple instances of a XFBML like button works fine though.. as seen here: http://www.onebe.at/de/kuenstler/
It might or might not be your answer but would it be because of the Open Graph properties? I noticed this in "http://luckyarts.de/liketest.html":
<meta property="og:url" content="http://www.luckyarts.de"/>
Update: Read the comments to the item marked as the answer below for the full answer.
I am implementing a Like button from Facebook per this document: http://developers.facebook.com/docs/reference/plugins/like
I am using the XFBML version so that users can add comments when they click on the Like button. I have imported the Facebook JavaScript SDK an am using a valid App ID. The button appears and I am able to "Like" the page, but I am never prompted for comments.
Is anybody else running into these issues? Anybody know of a fix?
Before I had inserted the correct appId in the FB.init() call to initialize the Facebook javascript SDK, the button appeared, I was able to "Like" the page like you, but saw no comment box either.
When I inserted the appId, but hosted the page locally, I got an error message saying that the page could not be reached (from Facebook's servers).
Finally, hosting the page on a public server made the buttons behave as expected: with comment box for the XFBML version, and without comment box for the Iframe.
Hope that helps...
add this style and the comment box will be hidden after you click like.
.fb_edge_widget_with_comment span.fb_edge_comment_widget iframe.fb_ltr {
display: none !important;
}
retailevovled is right. I've just found this tutorial which is a bit more detailed (German, but you can use Google Translate): http://www.be24.at/blog/entry/639312
Create an app for this specific implementation, then it will work:
http://developers.facebook.com/setup/
(I too first used an 'old' app-id with the same problems you described.)