Take a look on the screenshot above, what does the weird number represent?
I've seen this also. Seems to be a FB bug that happens intermittently. Those numbers should be city names. The bug seems to be temporary, but it keeps coming back.
Related
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!
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...
Can anyone explain to me what is happening in the following scenario?
I enter the following URL:
https://graph.facebook.com/search?q=United-States&type=place&access_token=MY_ACCESS_TOKEN&limit=1000
Facebook only returns 411 places and then when I execute the 'next' paging there are no places returned.
It seems like there is a limit or something stopping me from seeing more results. This is shown in both only showing 411 the first time and then the paging not working either. Has anyone encountered this and/or got a work around?
Thanks
From what it looks like to me, when I run this query, I only see places where I or a friend have liked that place.
In my experience, Facebook's location APIs are buggy at best.
If you're trying to find all the places, you're better off using a third-party service (I've been looking at Factual) to find this information, then query the Facebook API for the data you need about that info.
I have a number of dynamically generated like buttons on a site (http://www.thepropaganda.com), and so I use FB.XFBML.parse to generate them all. For some reason the parser always gets into a loop and repeatedly generates "domain and protocol must match" errors as per FB.SO Question 3577947. All the facebook social plugins are created correctly.
I understand what the errors are, and they're not really a problem, other than that there's thousands of them. Funnily enough this doesn't happen at all in incognito.
I'd really like to know what's going on here, as it's a live site for a paying client.
No idea why that's occurring but if it doesn't happen in incognito I'm assuming it's something to do with a cookie/session variable.
I would have added this as a comment but I need 50 rep to do it :(
I was used to getting datas from google places web service. But, This week I realize that web service link: https://maps.googleapis.com/maps/api/place/search/json?location=41.025414,29.114866&radius=5000&types=gas_station&sensor=true&key=XXXXXXXXX is returning "ZERO_RESULTS". It was used to return 50 places and I did not change anything on code.
When I remove types=gas_stations, it is working well. So, do you have any idea why "types" is not working well like it used to be?
I don't think you would have ever received 50 results as the Places API can only return 20 establishments at a time.
I would suggest trying the parameter types=gas_station at a multiple locations to make sure that is not working correctly, after which if you are still not receiving any results I would suggest filing this issue on the Google Places API Issue Tracker.
A temporary solution would be to use the keyword=gas station parameter. This appears to return relevant results.