polyisoprene

Twitter
Generated new access tokens. Seems to be working fine after the update.

Google+
I checked the “Visit Us” field. The URL stated there was slightly different from the actual profile page (http instead of https). Anyway, I’ve already made the necessary changes there, and updated the API key at the same time. The counter seems to be working fine now.

Thanks for the pointer. Looking forward to the new update to fix the Facebook problem too. Cheers.

P/S – One other problem, the counters for both Twitter and Google+ seems to be displaying the correct numbers while I’m still logged into my WordPress account. But the moment I log out, both the numbers go back to displaying “0” once again. I tried to clear the browser cache, but it still shows “0”. Is this a problem? Or is there some other residual cache somewhere that’s still displaying something from the recent past memory?

Thank you for your prompt reply. And thank you for solving the Facebook counter problem too. As for the others, the details are as below :-

Twitter
Consumer Key – 5xrgTSKwZmmN2PuVSEQI8OP9E
Consumer Secret – uB9X3SFWfzKdjPU7SqjwaDQHtxxYB7cl7JQDu6nYakhobV28BR
Access Token – 4065872304-0ne8TKpWdhKtORy6BND0UBONI53d7Hap8kFcpiz
Access Token Secret – 4rSIfjb07TLNowZdVGtV1HFvzMxAXexd4bKAAe7R08RGr

Google+
Google API Key – AIzaSyCGpy7sbl7WhdybTZeok_odwl8eYUv62UU

Looking forward to the new update. Cheers.

Thanks Matt. Good to know that there are people looking into issues like this. Don’t regret using Wordfence.

Cheers.

I experienced the same problem today. After calming myself down from a panic that my site might be a target of an attack, I did a quick look around, on Wordfence as well as the whole site in general. A quick check with the Wordfence Scan showed a “New Issue”, which was a plugin that needed an update. But the funny thing is that I had already updated it (first thing I do every time I login), so it shouldn’t even show up.

Logic would have it that any new updates would have removed the alert on the need of an update on that particular item. But when I checked it, the “New Issue” warning was still there. So I did a manual scan, upon which everything was indicated as clear. Then I did a check again. This time around, the banner at the top was cleared of the error message.

I don’t think this is a big issue, but for non-technical people (present company included), it might appear that the sky is falling.

I don’t know what happened, but after loading and reloading the home page over the span of several hours (using two separate mobile browsers), things seems to have sorted itself out.

Anyway, I’ve double check and triple check, on both mobile as well as desktop, and everything now seems to be working fine… Weird!… No help needed already. But thanks anyway.

Thanks for your quick reply.

Got it, they’re bots, and bots are bad. So do I manually remove them? Anyway, I’ve just added WordFence in my plugin, and it’s now scanning through my system.

Yeah, I’ve got WooCommerce added to my localhost website to play around with, and learn how it works. Came across several stone walls when exploring this new maze. But I guess if I persevere, I’ll be able to master the whole map eventually.

Letting WordFence do its job. If I come across another stumbling block, I’ll come back here again. But in the mean time, I’ll continue to enjoy learning this brand new experience.

Thanks again.

Cheers,
Wei-Ming

Thanks David. I’ll post it there instead.