Plugin fails to count any views.

It would seem that I was able to reach a conclusion to this subject.

By removing my local IP address (127.0.0.1) from the Exclude IPs list, and then visiting some of my earlier postings, I was able to get these self-visits to register eventually. But there are a number of factors which impede this plug-in:

I have the ‘JavaScript’ Counter Mode selected. There seem to be many browsers with JavaScript disabled. Yet, I’m not free to choose ‘PHP’ as my Counter Mode, because I use the plug-in ‘Memcached Is Your Friend’. This leaves me somewhat stuck.

The side-bar does not refresh, every time the Posts View / Main View refreshes. I actually needed to go into my Admin Panel and then come back out of it, before the recent self-visits showed in the widget.

What this means is that the data collected there can be misleading, and that it could confuse people. It’s only marginally useful to me as the Admin. And so what I’m going to do is to hide the widget from Guests, using the ‘Widget Logic’ plug-in.

I’m sorry that users will not be able to see the widget from now on, by following the above link.

Dirk

Thank you for the attention.

In my brief experience, there are many visitors to my blog who do have JS disabled, as I can see in the entries in

/var/log/apache2/access.log

Not having any Ajax calls. Yet, I feel that I have gotten your plug-in to work well for me now. What I did was to insert the following line into ‘wp-blog-header.php’ :

pvc_post_views( $wp_query->post->ID );

And to set the Counter Mode to PHP. That did the trick for me. Apparently, this bypasses the ‘Memcached Is Your Friend’ plug-in’s caching.

And you are correct. It is because I have the Object Caching of your plug-in’s statistics set to 10 minutes, this seems to be what introduces the lag, with which the widget displays views.

I now feel that your counter is working reliably enough, that I have removed the ‘Widget Logic’ plug-in widget logic, which used to prevent users from seeing the widget, who were not logged in.

And I do see that it’s normal, for the total number of HTTP requests to exceed the true, honest number of views. Hence the discrepancy between the two counters. Your counter now displays the honest number of views, while the other counter merely displays how many times the header has been called…

Thanks again,
Dirk

P.S. It is also a fact, that a large number of so-called visits to my blog stem from robots. And I appreciate the fact that I can filter out the robot hits from the count, which your plug-in offers. The other counter does not give me that option.