Hello, * Morbus Iff (morbus@disobey.com) wrote:
Implementing stuff like browser detection can be annoying, as you need to keep its database up to date to the latest browser releases. The best solution would be to find a good reference set that is easy to import and kept up-to-date. Though I agree with Moshe that Drupal's stats module should mainly be for Drupal-related stats. Webalizer tells me the
I'll +1 to this. The current stats are great for a quickie eyeball of today's stats, but if I really want something "professional", I'll just depend on my weekly analog stuff, which never gets deleted.
I think that the one thing that core should do is for watchdog to capture additional information such as the browser identifcation string, and just store it in the watchdog file. Then some bright spark can write a contribution module that formats the stats to get this information. As for browser detection, drupal should not do this at all. If they theme is that complex, then you can do browser detection in your theme to get around the problems. -- Gordon Heydon <gordon@heydon.com.au>