Site Update: Our Temperamental Facebook “Like” Buttons

| July 9, 2011 | 6 Comments

Facebook Like Button

Hey, folks.

Our Facebook “Like” buttons are being quite buggy and temperamental today. When you click on the button, you’ll either:

  • be able to like it and share the link on your wall (which is obviously what we all want)
  • be able to like it but then the button unlikes the post by itself (Facebook bugs, I say, bugs!)
  • be able to click on the “Like” button, which changes to “Confirm”, which then records your like
  • be able to click on the “Like” button, which changes to “Confirm”, which leads to a confirmation error when clicked

That said, we’re working our butts off on this one and have fired away some emails off to Facebook. It appears that this is a pretty common issue, but Facebook has yet to fix all the bugs on their end.

We apologize for the inconvenience this may cause some users, but we hope you’ll continue to check the site out as we work out the kinks. Thanks!




Read more cool stuff:

 

Tags: , , , ,

Category: Newsbreak

Comments (6)

Trackback URL | Comments RSS Feed

Sites That Link to this Post

  1. We Give Two Thumbs Up For These Facebook "Like" Hooks | July 17, 2011
  1. Phew, glad I found this article. I was just adding this functionality to a new site and was scratching my head at the results.

    Fingers crossed they fix it soon! :)

    • Haley says:

      I know, right? It drove our tech team nuts trying to find out what was up with the “Like” button.

      Glad we were able to help out in some way, though! :)

  2. Tried to add it too our for ka special offers page http://www.jennings-ford.co.uk/newsales/newcars/ka/ka.aspx but its was doing same thing do you think this will be sorted soon?

    Possibly facebook just launched it too quick to combat google +1 thingy.

  3. Way Fresh says:

    Looks like it’s working again for me :)

    • Haley says:

      Good for you! Most of our “Like” buttons are working again as well.
      Looks like Facebook has done a lot of fixing since the problem was reported! :)

Leave a Reply