I searched and could not find a thread on this.
I did find some that were confused by it though.
I am running a basic version of Piwik in a test environment.
When you select a date range (Say September 1014) the range on all the graphs (in every report) in no way reflects that range. Instead of a report that starts at sept 1 and ends on the 30th (expected behavior) I get a graph with 2 years of data.
If I wanted 2 years of data I would have asked for it.
This presents some serious problems:
1. There is no way to get the graph to actually display what you want it to.
2. Many posts I cam accross mistook activity on the graph for activity durring the period selected and reported errors in the detailed reporting. (it's super conrfusing)
IMO this is a critical issue. It may prevent us from rolling out Piwik as I can't actually produce a graph of data I am asked for.
"Show me what visits looked like in september" is as far as I can tell compltely imposible to do.
I REALLY hope I am just missing a setting or something. Is this a tracked bug? Did I screw up?
I did find some that were confused by it though.
I am running a basic version of Piwik in a test environment.
When you select a date range (Say September 1014) the range on all the graphs (in every report) in no way reflects that range. Instead of a report that starts at sept 1 and ends on the 30th (expected behavior) I get a graph with 2 years of data.
If I wanted 2 years of data I would have asked for it.
This presents some serious problems:
1. There is no way to get the graph to actually display what you want it to.
2. Many posts I cam accross mistook activity on the graph for activity durring the period selected and reported errors in the detailed reporting. (it's super conrfusing)
IMO this is a critical issue. It may prevent us from rolling out Piwik as I can't actually produce a graph of data I am asked for.
"Show me what visits looked like in september" is as far as I can tell compltely imposible to do.
I REALLY hope I am just missing a setting or something. Is this a tracked bug? Did I screw up?