Twitter, Pinterest share counts are 0 on all pages.

[goldenis]

Hi @jaredatch
http://blog.paleohacks.com/coconut-flour-pancakes/
the twitter, pinterest share counts are 0 on all pages.
on previous versions, it works well though.
Can you check why?

Thanks.

[jaredatch]

Twitter count was killed off some months ago by Twitter. That hasn't functioned since then. For this, we added the setting where 0 counts can be omitted, that way it doesn't show a fat zero.

We have a previous ticket that contains some possible unofficial 3rd party work arounds, but none of those have been implemented yet, see #39

Pinterest should definitely be working though. @billerickson has it working on one of his large clients. Can you confirm the Pinterest API is checked on the plugin settings page?

[goldenis]

@jaredatch Pinterest API was checked already.

[goldenis]

@jaredatch Can you check why PInterest still shows 0?

[jaredatch]

Pinterest counts should start to show up as the cache expires.

[goldenis]

I've disabled all caches from the site but still shows 0. are you using §like_count from PInterest responds?

[billerickson]

No, we're using count from Pinterest. This this result:

{"url":"http://blog.paleohacks.com/turkey-bacon-burger-recipe/","count":173}

[jaredatch]

Sorry, I should have clarified. The server cache isn't the only cache - EASC has it's own cache, otherwise the plugin would end up crashing the server from the requests.

Cache times depend on how old the post is (and are adjustable via a filter).

They should expire roughly over 24 hours or so.

See http://blog.paleohacks.com/edible-cookie-dough/

Also you can manually refresh the cache using the metabox on the post edit screen (https://cl.ly/1f3W1W1v2N13).

[goldenis]

@jaredatch Thanks for quick response.

I've already tried to refresth the cache using the metabox but it didn't work.

http://blog.paleohacks.com/coconut-flour-pancakes/

check the above link, please.

from the api, it's returnig over 100K counts but in meta box, it still shows 0.

[jaredatch]

@maybe there is a slight delay in the refresh. Shows for me https://cl.ly/1W3m3g1n3c1J

Also, I'm logged in, so I'm by passing the cache.

If you are not looking at the logged in you'll be getting the cached version, with the old (0) count.

[jaredatch]

Also, in a previous update, we changed how the refresh works to try to speed things up.

When a refresh is triggered, it returns the old (expired) counts, and then runs the refresh right before the server request ends.

So when you trigger a refresh in the metabox, even though the refresh is happening, I think it might be showing the stale numbers. I'll how to look into that deeper and see if thats the case or not.