StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLike Button Not Showing Counts
text
Body
copied!<p>This happens on any web browser. When I go to the page, I see the like button not showing any counts. Then I...</p> <ol> <li>Press on the Like button.</li> <li>I then see the box say +1. </li> <li>I refresh the page.</li> <li>I no longer see the +1 and I see the Like button as if it was never pressed. </li> </ol> <p>I can repeat steps 1-4 endlessly with the same results - I never see the total live count.</p> <p>It would seem like it's not keeping counts, but when I query it via:</p> <p><a href="https://api.facebook.com/method/fql.query?query=select">https://api.facebook.com/method/fql.query?query=select</a> total_count,like_count,comment_count,share_count,click_count from link_stat where url='https://www.myswebsite.com/'&format=json</p> <p>I see the live stats - so I know it's working. I've also tried different variations of <a href="http://developers.facebook.com/docs/reference/plugins/like/">http://developers.facebook.com/docs/reference/plugins/like/</a> - and old versions as well. I've isolated the code to just be the facebook code with nothing else on the page. For some reason, when I use <a href="https://www.myswebsite.com/">https://www.myswebsite.com/</a> it doesn't show. I try other URLs like <a href="http://www.google.com">http://www.google.com</a> with the code, and it works fine, I can see the count.</p> <p>It's an SSL web site. Does this have anything to do with it? Also, when we initially launched the site with the Like button, it was <a href="http://mywebsite.com">http://mywebsite.com</a> originally. Then we switched it to <a href="http://www.myswebsite.com">http://www.myswebsite.com</a>, and then setup a SSL wildcard to function with both. I'm not sure if caching has anything to do with it.</p> <p>Thanks!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload