Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with range of days pulling out for Actions.getDownloads report #5412

Closed
mgazdzik opened this issue Jul 4, 2014 · 2 comments
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone

Comments

@mgazdzik
Copy link
Contributor

mgazdzik commented Jul 4, 2014

It's been discovered that for some reason querying Actions.getDownloads report with self-containing set of days can produce different data for the same date.
I.e. querying period=day&date=2014-06-20,2014-06-30 returns some data for 2014-06-28. However after changing date parameter to 2014-06-26,2014-06-30 it gives different data for 2014-06-28.
After changing dates some more, it turned out that it was possible even to retrieve third distinct result set for this specific date.

@tsteur
Copy link
Member

tsteur commented Jul 7, 2014

Hi there,

I tried to reproduce this issue on demo.piwik.org without success. Have you experienced a similar behavior for other APIs such as Actions.getPageUrls? Would you mind having a quick test?

Can you reproduce this with any other date? EG "2014-05-20,2014-05-31" and "2014-05-26,2014-05-31"?

How many results within the result set are different approximately?

To actually debug and find this issue we might need access to your Piwik installation and maybe even FTP where the Piwik files are located. Do you think this would be possible?

@mgazdzik mgazdzik added this to the 2.5.0 - Piwik 2.5.0 milestone Jul 8, 2014
@tsteur
Copy link
Member

tsteur commented Jul 11, 2014

Problem does no longer occur in 2.4.0. Maybe fixed in #4872

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

3 participants