All geek questions in one place

New xfbml Like button + CloudFlare 503 bug killing score?

Recently switched to XFBML to make our page more efficient. However, we noticed that when we started using fb: for example, against the old iframe, the new Facebook Likes are no longer being recorded!

I would like to get some idea about this. The Facebook debugger does not return error codes, so we are in the dark about what causes this!

Link to the code, everything checks:

<fb:like href="http://www.example.com/" send="false" layout="button_count" show_faces="false" width="90" font="arial" action="like"></fb:like>

CloudFlare: I noticed that CloudFlare sometimes rejected traffic from Facebook debug / linter and wanted to know if this could be related? Here is an example query that you can try: http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.vancitybuzz.com%2F2012%2F01%2Fwhat-lurks-below -british-columbia% 2F

Thanks for the help!

Update: this problem occurs when using several methods for "like" (HTML5, etc.)

+2
source share
2 answers

It took a recipe to figure this out, but if you have the same symptoms (CloudFlare, Wordpress site, Facebook “How” button does not work in xfbml and html5 formats), then here is what I recommend:

  • Contact CloudFlare and request an update of all whitelists
  • Remove the CloudFlare setting to verify browser integrity.
  • Clear and / or change all cache control headers
  • Wait one day for CF servers to practice
  • Run linter / debugger reset to “like”, which lost count: http://developers.facebook.com/tools/debug
  • Add your Facebook id to the meta tag
  • Similar items you want to rejuvenate
  • Wait one more day for Facebook servers to distribute and synchronize accordingly.

The key point was the time of the problem, as CloudFlare and Facebook have extensive servers that require synchronization, and can take several days to catch up.

+1
source

We really identified the problem (worked with Facebook), and we believe that the corresponding fix has been fixed for this. Our internal tests and reports from other customers show that the problem with the 503 debugger no longer returns.

If you see other problems with the debugger at all, contact CloudFlare .

+3
source

Source: https://habr.com/ru/post/1392588/

More articles:


All Articles