DarkSafka

Is the Instagram authentication page in some other language rather than english? If so I have found a workaround for the problem.

Basically when you click the big blue “Connect An Instagram Account” button on this plugin’s settings page and you are redirect to the authentication url you have to add &hl=en to the end of the url where you currently are and press enter (to reload the page). Now the authentication page is in english and the authentication will work for some reason.

Thanks for the fast response! I had a feeling that the first problem wasn’t going to be solved that easily (making tables responsive in a smart way isn’t really the easiest thing to do in the first place) but that $default_atts thingy seems to work nicely so thanks for the help.

Same issue, I reported a few of the spam comments through here https://docs.google.com/forms/d/e/1FAIpQLSeQlKVZZYsF1qkKz7U78B2wy_6s6I7aNSdQc-DGpjeqWx70-A/viewform?c=0&w=1 Hope it helps.

Thanks for the reply and sorry for the wait!

I have already unchecked the “Validate the ip address of commenters” option and saved changes. Hopefully this solved the issue, at least I haven’t had any “Fake IP spam” anymore (then again there haven’t been any new comments from those IPs marked as fake).

Here’s two IP addresses that have been marked as “fake”:

192.228.170.82

83.150.82.74

The comments were completely fine though.

I have this exact same problem and haven’t found a fix yet. I tried disabling database cache but it didn’t help. For some reason it seems that logged in users views are getting counted like they’re supposed to be but no other views are getting saved to the database.

The views were counted correctly before enabling W3 Total Cache. I also tried adding post_views_count and wp_postmeta in the “Ignored query stems:” box under Database Cache Advanced Options (before disabling Database Caching completely) but it didn’t help either.

Disabling both Page Cache and Database Cache seems to get the post view count to work like it’s supposed to.

Same problem here. I like this plugin a lot and would love to continue using it so I’m hoping there will be a fix soon!