I do remember something about a possibility to exclude users from beeing counted, but I cant seem to find it. Where do I find it?

Comments

Gurpartap Singh’s picture

Gurpartap Singh commented

You can set role specific visibility using the visibility_api module. Instructions are provided on http://drupal.org/project/firestats

lomz’s picture

lomz commented

But how do I do it if I want it to collect information from all autenticated users and anonymus users except thoose that belong to a third role?

Gurpartap Singh’s picture

Gurpartap Singh commented

Enable Firestats and Visibility API module for Drupal 5.x.
Setup your roles(say admin) for whom you don't want to collect stats.
Assign this role to the concerned users, say user ID 1.
Setup Firestats and goto it's settings.
Select to only collect stats from anonymous user and authenticated user role.

That should get you right to the point. Hope that helps.

lomz’s picture

lomz commented

But since the admins is authenticated users; wouldnt this make them be counted?

Gurpartap Singh’s picture

Gurpartap Singh commented

But they are also admin user, which are meant to be ignored!
I have tested to accomplish the same.
However, if it doesn't work the way you want, maybe you can report to visibility_api module.

lomz’s picture

lomz commented

I just tested, and it seems like everyone got counted.

lomz’s picture

lomz commented

I created a spesific role for regular users and test with that, even if it is just the "regular" and the "anonymus" roles that shall be counted it counts my admin users that not belongs in the "regular" role

lomz’s picture

lomz commented

Visibility API told me too take it here: http://drupal.org/node/246411

lomz’s picture

lomz commented

Anybody looked at this?

lomz’s picture

lomz commented

Anyone? Or has the module been abandoned?

pomliane’s picture

pomliane commented
Status: Active » Closed (won't fix)

This version of FireStats is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.