About statistics : do not show administrator browsing

By Julien PHAM on 8 Jun 2006 at 12:18 UTC

Hi,
About all the statistics, the number of pages visited, the number of times a page has been viewed, and the like, is there a way to setup drupal to not count administrator browsing?

Thanks

Comments

Ignor administrator (user 1) hits

jsloan commented 8 June 2006 at 15:13

There are no "settings" to do this. You would need to add some code to the statistics.module in the function statistics_exit(). Since the $user variable is available inside the function just adding something like this just after the global declarations would work.

if ($user->uid == 1) {
    return;
  };

Here is my patch to

stefano@tipic.com commented 8 June 2006 at 15:34

Here is my patch to statistics_exit(), to skip views of administration pages, user pages and captcha images, or skip everything if user #1.

$paths = array('admin', 'user', 'captcha');
if ($user->uid==1 || in_array(arg(0), $paths)) return;

Thanks. btw do you know how

Julien PHAM commented 9 June 2006 at 08:34

Thanks. btw do you know how to clear the counter? As my site is under development, and i would like all pages to show 0 views once my site goes live.

clear the statistics

jsloan commented 9 June 2006 at 12:27

The easiest way is to go to the statistics settings page and drop the "Discard access logs older than:" interval to 1 hour. Change it back to where you want it when you go-live.

- or -
The statistics.module runs the following SQL statement via the cron_hook:

/* clean expired access logs */
 db_query('DELETE FROM {accesslog} WHERE timestamp < %d', time() - variable_get('statistics_flush_accesslog_timer', 259200));

So if you have access to your mysql database (phpMyAdmin) you could run this statement to reset everything to 0

TRUNCATE accesslog

I tried to truncate this

Julien PHAM commented 12 June 2006 at 07:31

I tried to truncate this accesslog, but when I go back to my website I still view, for a node : read 6 times, for example...

Go the easy route...

jsloan commented 12 June 2006 at 12:08

... by going to the statistics settings page and drop the "Discard access logs older than:" interval to 1 hour.

After one hour check it again. (This assumes that you have a scheduled job running cron.php at least once an hour). If in doubt just run cron.php manually.

If the access log is empty then you should not see any "reads". either the "Truncate" is not correct or the page is cached.

But your solution seems

Julien PHAM commented 12 June 2006 at 14:00

But your solution seems strange... imagine I want to discard access logs every 2 weeks. Does it mean for example, a page will be shown as read 5 times, then 10, then 20, and after two weeks this page will be shown as read 0 times, so never read? Seems kinda strange, and it makes me doubt this is what I'm talking about...

I think what I'm talking about is more the second page of this statistic settings:

Count content views:
Enabled
Disabled
Increment a counter each time content is viewed.

So I wonder where is stored this counter...

Back up a little bit...

jsloan commented 12 June 2006 at 20:52

Your question was "how to clear the statistics for a go-live" and my suggestions were to that point. Since you were not able to truncate the table I recommended the "settings" approach. Set the time limit to one hour, go to lunch and when you return after the one hour your statistics should be clear... assuming that there was not any other visits and that your cron.php had been run.

In practice the settings will delete and statisitcs OLDER than the limit set. So after two weeks you will see statistics for only the last two weeks ... not zero - unless of course no one visited your site in those two weeks.

But I was not talking of the

Julien PHAM commented 13 June 2006 at 09:29

But I was not talking of the statitics where they say what visitor visits a given page, I'm just talking about the counter, you know, the one that is displayed with any node and says how many times this node has been read.

Clearing the counter

jsloan commented 13 June 2006 at 12:17

The individual node counter statistics are in the table node_counter. Executing the SQL statement TRUNCATE node_counter will clear all of your node read totals.

Thanks

Julien PHAM commented 14 June 2006 at 06:11

Thanks

I'm glad you have a patch

GreenLED commented 26 July 2008 at 04:40

I'm glad you have a patch for this. My one question is: Where do you place this in the "statistics_exit()" function. Do you place all inside code inside this logic or .... ? If you would copy / paste the entire function you have that would be VERY helpful to me. Thanks in advance.

» Respectfully, GreenLED
» Download Spybot

Add me to the list of folks

Eric Cosky commented 12 October 2006 at 15:37

Add me to the list of folks who would like to have some minimal control over what gets added to the statistics tracking. My site is small and robot hits are the majority of what I get, and second to that is my own hits that happen while I navigate around.

It seems like it would be very useful to have the option to exclude your own account from statistics tracking, or possibly exclude the submitter from being tracked for their own content. It seems reasonable and simple enough to at least exclude the submitter from being tracked in their own statistics for viewing their own content since that's a very common thing for people to do as they consider modifications.

Being able to exclude robots through some rule system, which I don't think could ever be 100% accurate given how bots tend to ignore rules, would be helpful in allowing those of us interested in reducing tracking statistics we aren't interested in to affect what data is stored.

IMHO the statistics module should record the statistics the admins are interested in as opposed to logging everything that a statistic could be derived from. My own host charges flat fees based on consumed bandwidth and disk usage and I'd prefer to not persist data unless I expect to use it since there is a very real (albeit small in my case) dollar cost involved.

- Eric Cosky

It appears the

Eric Cosky commented 5 December 2006 at 18:10

It appears the statistic_filter module provides this functionality. Yay :)

here we go

physiotek commented 19 September 2007 at 05:09

the statistic module is not working for drupal5. but i found how to acheive this here:
http://drupal.org/node/129971
enjoy;)

Is this a drupal 5 version

summit commented 14 February 2008 at 21:44

Hi,

I solved the recent hits without superadmin/first user logs with the SQL query on function statistics_recent_hits()
changed the sql to:

 $sql = 'SELECT a.aid, a.path, a.title, a.uid, u.name, a.timestamp, a.hostname FROM {accesslog} a LEFT JOIN {users} u ON u.uid = a.uid AND u.uid != 1' . tablesort_sql($header) ;

.

filartrix commented 1 November 2007 at 10:36

Is there any way to exclude sigle IP from statistic?

filartrix commented 1 November 2007 at 10:35

Hello, thanks for this hint, now i would like to exclude Google IP (66.249.72.5) from my website...
I have activated google analytics module, so Google always visit my website, to check the visitor number i think... and when i go to see statistics there are lot of double entries, one from the visitor, and the other from google... And also in "Recent log entries" i have lot of access denied warnings because of Google, i would like keep using google analytics (because of the localization of visitors), and the statistic module (because of the ip of visitors)
Does anyone can suggest me anything? Thanks

How to prevent certain IP(s) from incrementing the node counter

gmayes commented 4 April 2008 at 00:19

Hi,

I don't have a patch but hopefully some super easy PHP that you can add to your statistics.module so that the IPs you specify are excluded from incrementing content / node views. I added this to my Drupal 5.2 site (I don't think the statistics code has changed much, so you should be able to use this for 4.x and 6.x, hopefully) and it works. Before the line "db_query('UPDATE {node_counter} ..." in the function statistics_exit, add these two lines:

      // Don't increment the node counter for these remote IPs
      $hosts_to_ignore = array('66.34.234.121', '10.16.67.78');

and then wrap the db_query UPDATE in this if:

      if (!in_array($_SERVER['REMOTE_ADDR'], $hosts_to_ignore)) {}

so the whole thing looks like:

      // Don't increment the node counter for these remote IPs
      $hosts_to_ignore = array('66.34.234.121', '10.16.67.78');
       if (!in_array($_SERVER['REMOTE_ADDR'], $hosts_to_ignore)) {
          // A node has been viewed, so update the node's counters.
          db_query('UPDATE {node_counter} SET daycount = daycount + 1, totalcount = totalcount + 1, timestamp = %d WHERE nid = %d', time(), arg(1));
      }

To customize this snippet all you need to edit are the IPs. Feel free to use only one IP or as many as you like, separated by commas.

Regards, Geoff

English

Nebraska USA

commented 2 September 2008 at 07:57

There is also the Statistics Advanced module that also provides this functionality.

About statistics : do not show administrator browsing

Comments

Ignor administrator (user 1) hits

Here is my patch to

Thanks. btw do you know how

clear the statistics

I tried to truncate this

Go the easy route...

But your solution seems

Back up a little bit...

But I was not talking of the

Clearing the counter

Thanks

I'm glad you have a patch

Add me to the list of folks

It appears the

here we go

Is this a drupal 5 version

.

Is there any way to exclude sigle IP from statistic?

How to prevent certain IP(s) from incrementing the node counter

Page counts are in node_counter table

I'm glad you have a patch

Statistics Advanced Module

New forum topics

News items

Our community

Documentation

Drupal code base

Governance of community