.changes is limited to 500 entries (hard coded). On some sites it's easy to get 500 changes between runs of WebStatistics
, so the statistics get out of date and inaccurate.
Rather than limiting .changes there are a couple of options:
- Make the cron that runs WebStatistics and MailerContrib rotate the .changes
- Limit on the basis of age, instead of number of entries (discard anything over a month old, for example)
I think I saw some work done on this one once - bug still real?
Still alive and kicking
Just not too important, so dropping to Low.
Fixed in MAIN. I changed it so it keeps changes up to a time horizon defined by an option in
Cleaned "WaitingFor" field.
- 10 Aug 2008