Add permission to bypass monitoring

Another thought is to count multiple visits from a single ip only once. This way the stats won't get 'polluted' by test visits during the site development. This could be made an option (a.k.a. checkbox in the module's settings page) as well.

Any thoughts people?

...glad to see this is getting some attention. A year after! ;)

I'm quite surprised at the fact that there are more than 4600 sites using this module and nobody has commented for so long.

...btw, this one and #650588: Add permission to view reports are the main reasons I stopped using the module in my latest setups.

I know that complaining does not get things done Greg, but there's a good reason why in my profile it only states 'I help in the Drupal support forums' and there's no 'I contributed Drupal modules'. If I could 'speak drupal' fluently, I'd be happy to provide a patch for each of my feature requests, but I am afraid I am far from that point still. I'd say that at this point I am a little over the 'I kick ass' threshold ;)

I am! Just been too busy these days. I'll try to find some spare time (if such a thing actually exists) to test and report back.

Ok, I've made some time to test #8, but there is still no way to exclude the site admin (considered one of the authenticated users).

Thanx for taking the time to reply Alex. I do understand the logic behind this and how roles are excluded (this might not be an issue for D7, since more than one users can be assigned the admin right/role). Perhaps the title of the issue is misleading but I was talking about checking against the logged in user's id and not the actual ip they come from (which can vary each time as you point out). I was more thinking/talking about:

*before ip is logged in the db* check against user id
- if uid = 1, then do not log ip in the db
- if uid <> 1, then log ip of current user in the db

Of course there has to be an option in the UI. Something like 'Do not log site admin's ip' or 'Exclude site admin from statistics'.

Oh, I didn't mean that your patch in #8 did not provide some useful feature Alex. It really does, because others might want to only log specific roles. So, give me some time to test your new patch that does what this feature request initially was about and then perhaps we can merge these two features(?) for a more complete feature set that will cover all tastes ;)

Thanx for all your time and effort on this.

#16 works as advertised (setting this to RTBC since I seem to be the sole person following the progress of this request)! Thanx ;)

We won't need to go this way for D7, because as I've already said in #15, D7 uses role id (rid field in the role table) in order to be able to assign the site admin role to multiple users. So, in D7 the monitor-by-role way (patch in #8) will suffice.

@greggles, #19: not that I intent to argue or anything, but consider this: it might not seem like a lot of 'static' in the stats of a high-traffic site where the say 100 hits of the admin per day might be relatively non-important compared to the hundreds of thousands of hits of other visitors, but in low-traffic sites (like those in early development stage) having only 100 hits from other visitors and 1000 from the site admin does lead to misleading conclusions of which browser is preferred by actual visitors. This request was based on an actual problem I faced. It was not a simple 'it would be nice to have' thing.

As I said I seem to be the only one in need of this, so I won't argue if 'worthwhile' = not-popular. OTOH, it would be ungrateful of me to agree with such a comment when I know that Alex has spent his free time in order to do this -perhaps only- for me. I guess what I mean to say is that Alex has at least one 'happy customer', so if 'worthwhile' = useful, then I think it is worthwhile.

Fair enough Greg.

...minor typo in issue's title.

I'll try this as soon as I get a chance.

@Rob: a couple of questions though:

- Is this against 6.x, 7.x, both?
- I simply want to point you to posts #13 through #18 besides #8 (#16 has another patch). Especially the d7 vs. d6 admin user thing (multiple users assigned to the admin role in d7 I mean). Did you take that under account?

Thanx in advance for your time.

...haven't actually tested it yet, but looking at the code I can already see the benefit (far less code) in using the user permissions page instead of the module's settings/report page + I think it does take care of the d7 multiple admins thing too. Might not be the best place to have it though (thinking usability-wise)...

1st case (checkbox in the module's page): User realizes the issue -> ticks the 'exclude admin(s)' checkbox -> saves. Done!
2nd case (per-role checkboxes in permissions page): User realizes the issue -> needs to visit the site's permissions page -> ticks on the checkbox(es) -> saves -> goes back to the report page to actually see it working.

A major difference between these two ways to approach this issue (feature-wise) is that by going the permissions way multiple/various roles can be excluded from the reports (instead of admin(s) only).

Thanx Devin! ...one less patch to "babysit" ;)