Ethos

Anyway, this was a one time alert only; it’s not showing anymore.

Everything is updated. WP-SpamShield Version 1.9.13.

I made a screenshot:

The alert says WP 4.7.5. Down at the footer, we have: “Thank you for creating with WordPress Version 4.8”. Didn’t think I actually need to offer a proof.

Hi,

I get the same alert, saying my site (https://sunlog.ro/) is running WordPress version 4.7.5, which is vulnerable.

My site, however, is runing WordPress 4.8.

Thank you for your prompt answer. As a completely free alternative solution, I’m also experimenting with Zapier and alike, in order to copy any new Dropbox file to Google Drive, automatically. But then I’ll need to manually delete old files from Google Drive, when they are too many.

Thank you for the replay, Ryan.

If I deactivate all the plugins, Facebook profile images will of course not be visible, because they are handled by Jetpack, which is a plugin! ?? But I disabled all the plugins, except for Jetpack. No change.

So I enabled all the plugins and switched to Twenty Sixteen. Tadaaaa, Facebook images are now visible.

So it seems my theme is the culprit. It is an old, free theme, and I don’t think I’ll have much luck asking for help on author’s site. Could you please guide me a bit forward from this point?

Thanks again!

also, my friend told me she normally had around 50 spam comments per day, when using akismet.

Hi, @girlieworks! It’s not a bug, it’s a feature! ?? Ok, I got it. Time to add new filtering rules, then! And yes, I put a [Bug] there hoping it will draw more attention, lol.

Thanks for the clarification. ??

• This reply was modified 8 years, 2 months ago by Ethos.
• This reply was modified 8 years, 2 months ago by Ethos.

Thanks!

Thank you for reply. This does indeed clear things up. And true, the counter is working allright for new blog posts.

One last question: why is Jetpack throwing that

“Uncaught TypeError: Cannot read property ‘share_count’ of undefined”

for old posts? I mean I know it’s no bother for the reader, but isn’t a sign of a perfectible code?

Unfortunately no, it does not work.

I followed the steps presented there but now, when i click Connect, I get the following error:

“Something which should never happen, happened. Sorry about that. If you try again, maybe it will work.
Error code: -10520″

I should also mention that I just switched from http to https (secure connection).

@jeremy Herve

Ok, thank you for the response. ??

Same here, I had 80 Facebook reactions at https://sunlog.ro/2016/07/iuliu-bakcsi-este-plagiator/, now there are zero. Same for all other articles from my blog: https://sunlog.ro.

@jeremy Herve

Does this has anything to do with Facebook deprecating it’s old API? Because if it does, this are bad news imo, meaning other Jetpack code may also be close to obsolete. Facebook told developers it’s going to deprecate this API some time ago. And you’re updating only now? When the old code it’s no longer working?

??