First post on StackOverflow, so please forgive any protocol lapses!
I've found similar problems to the one below elsewhere on SO, but none that's an exact match, nor a solution that hits the spot.
I have a client site with FB Share and Like buttons, all of which work perfectly on straightforward named pages. In the case of the shop and blog pages I need to use a querystring, which works perfectly on other sites, but not this one! I've run the FB Debugger on the affected pages and all looks hunky dory.
Here are two example pages with the problem:
http://www.fabniki.com/productdetail?pid=251 and http://www.fabniki.com/blogdetail?id=327&p=1.
In the case of the shop item, the text Facebook is showing isn't even on the page. I've tried clearing cache, forcing an FB cache refresh etc.
My own site uses a similar querystring system for my blog, and this works absolutely fine with Facebook shares and likes.
I'd be very grateful for any suggestions!
OK, the problem was - unsurprisingly - entirely of my own making. I'd allowed myself to get bogged down in the debugger, which looks at the exact URL you paste into its input field. If you're sufficiently idiotic, it may not occur to you to check if this is the actual value being passed to FB by your Like and Share buttons. Doh!
Thanks to some excellent support from FB developers, the problem was spotted and corrected with only minor dents to my ego.
I wanted to answer my own question, a) to avoid wasting people's time and b) to give Facebook Support a bit of appreciation for a change!
Related
I am using this embed code for a site. The site is a Django site. I apologize if my terms are wrong, I'm not a developer. . Periodically I return to the site and the graph will not display, but the logo from the host site does. I suspect that it's a caching issue. I tried "no-store" but I'm not sure if I pasted it in properly.
I want to add a random number generator to the embed code. In my mind that would be similar to a refresh - again, not a programmer. Django strips css and possibly more. Can anyone either solve my problem or write the random number generator to make the "border-width" 1, 2, or 3? Here is my site with the bug. https://www.twelvebridges.com/twelve-bridges-market-report/. I encounter the bug on Chrome on a macbook. Never the first visit and a refresh solves it every time.
I tried "no-store" but probably in the wrong place. I tried Classic Cache Killer as a Chrome extension on my site. I added a gif on the site even though I cannot really articulate what I thought that would accomplish.
Can anyone provide a workaround for this bug
Our app is managing a lot pages with many posts, but since 5 days ago we've had huge problems with that bug.
90% of our posts gain the above described error, 10% are working well.
After many hours of testing we know it's something about the "link" parameter.
Without it, we can post without any errors.
We tried to only post our images without the link parameter but after a hour of posting correctly we got a new error.
(#368) The action attempted has been deemed abusive or is otherwise disallowed. Interesting that posting an image without a link parameter is abusive.
We tried to regenerate all user_tokens and page_tokens but no success, the error still exists.
We tried to pause the service for 24 hours and start it again, no effect.
Does anyone have an idea or a workaround for this bug?
It doesn't seem that it was patched on Tuesday. Because of that we need a solution, we can't hold the service down for one more week.
the workaround from "thefreeman" works for me also:
add more admin(s) to the pages
generate tokens for the new admin
juggle the tokens to stay below limit
Limit per account (for me) seems to be about 150 posts per day.
Limit seems to reset at a certain point in time. Midnight at facebook?
(i am managing 60 Pages and posting roughly 200 updates per day.)
certainly not a nice solution, but the bugs in the fb-bugtracker don't seem to get too much attention :(
sometimes i get a new error: "OAuthException (#1500) The url you supplied is invalid".
Trying again later with the same data works though...
This is my first post here, so forgive me for stupid questioning or describing my problem not „the programmer's way“. :-)
I've added Facebook comments to my Wordpress blog. Now, I posted a test comment with another Facebook profile than the one I used to create the app.
Voila, the comment appeared on the Graph API of that site. Worked well.
I deleted the comment, but it seems as it's still visible in the Graph API of the site.
Is there any cache for deleted comments!? How can I fix that?
It's important for me to know, because I think of a contest. Users have to add captions to pictures via the Facebook commentbox.
It doesn't give me any benefit, if comments that have been deleted will remain in the Graph API.
Any solution for it? What else do you need to know what I'm talking about? :-)
Cheers,
Axel
You can't delete comments, that's a bit bad documented. All you can do is hide it from other users. Every fb user that is a friend of the user that posted that 'deleted' comment can see the comment as well as the user himself too (in the actual fb comments box).
Furthermore it will exist forever in the graph api! That's facebooks way of pushing freedom of expression!
Anyway if you delete content it doesn't sound like a fair contest to people, as they might feel objected, also not everyone will have the same chances then. A system where you can properly approve 'comments/captiions' would make way more sense. See Diskus for example.
If you wanna have the facebook comments social advertising boost though you could write all comments from the graph api into a database and then approve them manually. Another way would be just to tell users to subscribe/like your facebook page to see who's winning or to be able to win at all. Good luck
I'm using the comments box on my site to get more users socially involved and at the same time I'm reading the Graph API to print those comments on the same site to make it crawlable for search engines. Problem is now that for a real user the comments show up twice (through my graph api print AND through the actual fb:comments plugin box).
Any ideas how I could solve this ?
Would prefer to show only the comment-field from FB and use my own echo to show the comments as this way enables it to REALLY moderate the comments (not just set it to limited visibility). Thanks for any suggestion!
I found some sort of solution for my problem. It's not perfect, but the closest one can get to what I wanted:
Instead of directly returning the query from the Graph API, I attached a script to the comment.create event. This script writes the new comment into my database, where I can moderate again. This way I have to double-moderate, but therefore I don't have any unwanted comments on my site.
I also found out that with the old deprecated comment-box you can set the comments that get natively shown by facebook to 0. That way only the already moderated comments get shown by my own script coupled with my database. It works the way I want it, even for friends of the unwanted commenter.
Hope that helps someone else too!
I am looking for a blogging and comments system that can smoothly integrate with my Django sites. I've found there is a lot on the Net and got lost a bit, and I don't have much experience on this. Hope you guys can give me some suggestions.
Here are the things that I would like to have:
Tag Clouds
Articles Archive (by months/by years)
Articles Rating (e.g. with Stars or customize icons)
Comments to the particular Topic/Articles
Sub-Comments of a particular comments (i.e. following up comments)
Blogs/Articles Searching
Able to relate other articles that is relevant (i.e. follow up Articles)
Pagination of the comments if get too long
OpenIDs supports (e.g. facebook, hotmail, blogger, twitter...etc)
Support login before user can comments
Able to retrieve Blogs' Header and customized the display order
Able to subscribe this article to RSS
Able to Email this to friends (this may not belongs to the comments system)
If I missed some common functions, please let me know. The comments system I am looking for should do most jobs that those popular comments system should do on the web, e.g. WordPress.
Thank you so much everyone. Have a nice day.
I myself really like django-threadedcomments. It supports threaded commenting like what you would see in Disqus.
i heard django-comment-utils is quite good. - may you test it :)