Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This module needs noscript support and I have attached a patch that implements that.
| Comment | File | Size | Author |
|---|---|---|---|
| piwik.noscript.patch | 587 bytes | jurgenhaas | |
Comments
Comment #1
hass CreditAttribution: hass commentedComment #2
jurgenhaas@hass, any reference to the duplicate ticket please?
Comment #3
hass CreditAttribution: hass commentedhttp://drupal.org/project/issues/piwik?text=noscript&status=All&prioriti...
Comment #4
jurgenhaasWell, that's the list I searched for before submitting this ticket and all tickets for the 7.x release are closed and the two others are related to the 6.x release where the implementation would be completely different. Therefore I suggest to re-open this ticket again, but I leave that decision to you as the module maintainer.
Comment #5
jurgenhaasSorry for reopening this issue bute as I wrote in #4, there is no other ticket addressing this for D7 and I think it is a major issue too as tracking without noscript support is pretty meaningless.
Comment #6
hass CreditAttribution: hass commentedMaybe this status makes it more clear what the most people think about NOSCRIPT tracking if they know how bad is clutters statistics with non-users aka robots, etc...
Comment #7
jurgenhaasAre you kidding me? There are many security-conscious internet users out there and you want to tell the Piwik community that they should not be tracked? I don't think a module maintainer should be in such a strong position, he should at least provide an option to the users of the module.
Comment #8
hass CreditAttribution: hass commentedCheck your own statistics, please. Look for how many people have JavaScript enabled or disabled. After you spend some time how tracking worked ~5-10 years ago (log file analysis) and you spend the time to find out how wrong the results are and if you found out why all tracking tools have started to use JavaScript to track REAL humans and you compared your Piwik/GA with a logfile analysis like AWStats (typically 1000% of Piwik/GA counters), than we hopefully don't need to discuss this further.
But before you waste a month to learn. JS disabled users are less then 1% and this <1% are partly not users. As web-visitor statistics lie *all* in general and they are never 100% correct, you can be sure the 1% is not a number that will change your statistic nor gives you a different picture of how you site works or works not.
It's a waste of time to develop this useless feature and it would only *clutter* you statistics; if we track noscript hits. I know there are some pedantic people who think they may miss "one" user from tracking, but they are all not aware of some technical realities or think the counters in their statistics are the real numbers. Dreamers...
This being said with nearly ~20 years website statistics analysis experience and not only my personal position. Google Analytics, Webtrends, Overture - all are not providing this out of the box for good reasons. There is no need to waste time with something that does not provide you answers about your website.
I really hope this is the last waste of time discussion about this feature.