Veken

Thank you!

I am seeing the same thing as well. Admins & Editors can see all posts, but Authors or Contributors cannot see their own posts or drafts.

Thanks!

Thanks for the quick reply! looks like it’s still missing the closing apostraphe on the first term here:

‘shared_counts_preserve_http, ‘shared_counts_maybe_preserve_http’,
should be
‘shared_counts_preserve_http’, ‘shared_counts_maybe_preserve_http’,

I noticed the code in the last line of this filter had a few typos
https://github.com/jaredatch/Shared-Counts/wiki/Preserve-HTTP-Counts

add_filter( ‘shared_counts_preserve_http, ‘shareds_count_maybe_preserve_http’, 10, 2 );

should be

add_filter( ‘shared_counts_preserve_http’, ‘shared_counts_maybe_preserve_http’, 10, 2 );

add closing ‘
and “shareds_count” should be “shared_counts”

Hopefully that is correct.

• This reply was modified 6 years, 7 months ago by Veken.
• This reply was modified 6 years, 7 months ago by Veken.

Thanks! that worked.

I’ve added that second edit, confirmed the new code is live, and cleared all caches and it doesn’t seem to work. It doesn’t show any counts over < 100 or 1k.

If I remove the function all the counts come back.

Thanks! you predicted my next question about total counts. since we are only showing the total, it makes more sense to include the actual total vs just for the buttons shown.

I’ve updated the code, but it still doesn’t work. With the new function, a post with 3K shares shows nothing. By setting the minimum to 4 and then 3, I can see that it’s still counting 3k as 3.

Thanks for your help.

Thank you!

I think the code is just missing a closing ) at the end.

Thanks that fixed it immediately.

Thanks. I just wanted to clarify that the one post that appears is always the last published post. Which is not related to popularity.

This only appears when logged out. Is that a public default if no posts are in the list?

We are having the same issue and it’s been about 24 hours already since the update.
https://hyperallergic.com

This seems to have been fixed in version 3.0.1

This seems to have been fixed on our end since the last update. ver 3.0.1

This seems to have been fixed since the last update. Thanks