The same here. It looks like it has a problem in Grow > Settings > General Settings:
This code appears in Settings:
<div class="dpsp-setting-field-wrapper dpsp-setting-field-button dpsp-has-field-label"> <label class="dpsp-setting-field-label">Refresh Bitly Groups</label> <a href="/wp-admin/admin.php?page=dpsp-settings&refresh_bitly_groups=1" id="dpsp-bitly-authorize" class="dpsp-button-secondary"><span>Refresh</span></a> <div class="spinner"><!-- --></div> <div class="dpsp-setting-field-tooltip-wrapper "><span class="dpsp-setting-field-tooltip-icon"></span><div class="dpsp-setting-field-tooltip dpsp-transition">Refresh Bitly groups to see any recent changes made in Bitly.</div></div> </div>`
It’s between “Bitly Group” and “Purge Shortened Links” fields.
I hope this helps the devs.
Actual version: 2.14.1
Hey @marthaki,
Thanks so much for reaching out to us about this! We’ve noticed over the last couple of weeks that Facebook share counts may return as 0 for some (but usually not all) posts on a site. Since that is the number the Graph API for Facebook is returning, that is the number Grow Social will use when displaying/updating counts for a post on your site.
As far as we can tell, Grow Social is correctly requesting share counts from Facebook’s Graph API but there seems to be some issues with one of Facebook’s more recent updates to it. Whether or not this was an intentional change is hard to say, but issues have been opened with Facebook’s developers to have them take a look into this.
We don’t have any sort of ETA on when something like this would be fixed on Facebook’s side of things but we’re hoping they get this taken care of ASAP!
Hey @ruisamuel,
Thanks so much for pointing out that error! This shouldn’t actually impact the share counts not being returned from Facebook but the error is something we definitely noticed with our last release.
Just as a quick update, we do have a fix planned to take care of this in our Pro version’s 2.14.2 release. 🙂
Hey everyone,
Since the Facebook share counts are returning incorrectly is something coming from Facebook’s side of things we’re going to go ahead and close this topic. If you have any future issues please don’t hesitate to start up a new thread!
