Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

piwik.js: setDoNotTrack() broken #2847

Closed
anonymous-piwik-user opened this Issue · 4 comments

3 participants

Anonymous Piwik user Stefan Giehl Anthon Pang
Anonymous Piwik user

Hi,
I'm using Firefox 9.0.1 with default setting and Piwik 1.6 French version.
I can't see my visits in log visiteur with this browser and maybe with precedent version ( today i've the latest).

Stefan Giehl
Collaborator

I can't reproduce your problem with firefox 9.0.1 running on win7. In my piwik 1.6 installation all visitors of the selected day are displayed correctly. Would you mind to describe the problem a bit more detailed?

  • Are there any javascript errors occuring
  • is the page displayed correct eg. is only the list of visitors empty?
  • Might it be possible that your page just didn't have any visitors on the day selected in date choooser?
Anonymous Piwik user

My firefox is running on XP.
There is no javascript error and the piwik code is well present in the displayed page.
The list of visitors is not empty: no log only from my firefox 9.0.1 browser.
From the same machine with IE, I haven't problem.

Anthon Pang
Collaborator

Normally, I would close this and direct the reporter to post the question in the forum.

In this case, please email us at hello (at) piwik.org with your web site url, piwik url, and login id+password to your piwik instance. And please include a reference to this ticket.

Anthon Pang
Collaborator

The problem is that you're using setDoNotTrack. This is currently broken in 1.6 because Mozilla didn't implement it as they originally spec'd it. They have now updated the documentation to reflect the as-is implementation, and we have fixed this in trunk for the upcoming 1.7 release. [5592

Download the latest version of piwik.js from: https://github.com/piwik/piwik/blob/master/5664/trunk/piwik.js

Anonymous Piwik user anonymous-piwik-user added this to the 1.7 Piwik 1.7 milestone
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.