Hi all,
There is not only TOL, but MOW having dificulties with webalizer, so the
question is, if there is some place for tracker inside campsite.
I have to say, that developing the tracker is in strange state and all
my worries to this topic came trueth:
1) We collect all info we can
2) database is growing very quickly
3) optimalization of the code does not bring very good results
4) after more than year we still are on the road with no usefull output
5) We have to jump from developer to developer with no real success.

Therefore I would like to ask, if there is some way to get out from this
circle.

My idea is, to run away from supertracker, which over the year is more
like "Komunism" for me (All are trying to come to it, but noone really
knows how to do that and in current world I am afraid it is something we
cannot get) and make small, but precise stats inside the campsite.

I would start with something like counters, which will bring the basic
info. The counter would be extra field in article and in publication
(iand may be in user). Template language would allow to put counter
checker to template and all it does is, when parsed, it increases the
counter by one.

That would allow to display basic info - how much impressions the
article/publication had since last counter reset.

As a second step I would create some stats page, that would give a
precise info, how many times the issue templates were parsed, how many
times the selected articles were parsed, but may be also how many times
the user was logged in, hor how many pages were visited by subscriber.

All these info is possible to get from counters, if designed properly
and cover 99% of needs.

The fact is, that once per selected period we will generate some basic
info and zero the counter.
I can imagine, that publication counter would be zeroed daily
I would allow editor to turn article counter on and off and put stats
period in actions. The major reason for this is tracking how many people
red announcements, I feel the usage for all articles this would be too
huge.
On the user I would do weekly reset.

The thing is, that using this definition you have some standard amount
of data in campsite that is neaded for stats and you generate static
page for predefined tasks.

I believe no demographic info is neaded, because all that stats you can
get from webalizer and you definitely do not need precise numbers of
visitors from Tajikistan, you simply need to know the share. And those
numbers are OK in webalizer.

Ondra