Plugin Contributor
Ryan C.
(@ryancowles)
Hi there! I had a look at your site, and Jetpack appears to be properly connected at the moment.
Could your please provide me with links to specific posts that you notice the issue with share counts on? And have you made any recent changes to your site or your domain name?
Just let me know, and then I’d be happy to investigate further!
Sorry for the delay… In all my posts, including images, likes buttons (like this:) are not loading anymore – are after share buttons, which are visible now. For exemple:
1. post :
2. image :
Hi @dancaragea
We did have a previously documented problem with share counts but it has since been fixed. As I browse your site I can see share counts and like counts on every post I visit.
Here’s a screenshot of what I see on this post
Since I’m not able to duplicate the problem I think you’re having, I wonder if possibly you updated Jetpack recently and it solved the problem? If not, and you’re still experiencing the issues please let me know more and I’ll dig deeper to help you solve the problem.
thanks,
Jesse
I updated Jetpack – version 3.4.1 – as I said. Not happen until then. This problem it’s happens for all browsers for few hours and then is OK once again. But for URL attachments to posts is not working if at all.
I have a fresh attachment URL: and still more that are same.
Thanks a lot, anyway, for cooperation.
But for URL attachments to posts is not working if at all.
I was able to use the Like button on this attachment page:
http://i.wpne.ws/aZPo
If you continue to experience issues, could you try to log out of your WordPress account and let me know if the problem is limited to logged in users, or if it also happens when you’re logged out?
If that doesn’t help, could you please try clearing out your cache and cookies?
http://en.support.wordpress.com/browser-issues/#clear-your-cache-and-cookies
Let us know how it goes.
I logged out of WordPess account and I checked a few attachments. Now I can see like button for all. So the problem is limited to logged in users, like you said.
Thanks a lot!
I marked this topic as resolved, if you don’t mind.
So the problem is limited to logged in users, like you said.
Alright, thanks for checking. We’ll work on getting this fixed in a future release. I’ll post again here when I have some news!