When one tries to export data from line higher than or equal to 25 in a row evolution, you get no data.
Exporting from a row evolution from line 1 to 24 works well.
The URL behind the export option contains query parameter: "&filter_limit=#INT#" where #INT# is 24.
I've seen cases where #INT# is 100.
I'm using version Piwik 2.0.2.
Thanks for the report. I have not reproduced yet, can you please explain exactly the procedure you use? What is the export URL created?
The URL that exports no data:
The URL that does export data:
It looks like the filter_limit is the reason it does not export data. I don't know what triggers the filter_limit to be added. I used this export function from a row on the Xth pagination page.
Can you please explain exactly what you do in the user interface? do you open Row evolution? Then what do you do next?
I've added some screenshots that might explain the issue a bit more.
It can be reproduced on the current demo piwik environment.
Go to Actions ->
Page Titles ->
Second page, somewhere in the middle select row evaluation.
Choose export to CSV.
The Exported file only contains the word 'Date'.
Do you have any news on this?
I have trouble with the same thing. Reading this bug i have seen, that i also have a duplicate filter_limit parameter. Once with false and once with 10.
When i remove the parameter with 10, the export returns a correct csv.
Otherwise it returns only "Date".
It seems that there is only a problem for the period year, but it works with month.
And it works with different URLs (period year) and there are 2 filter_limit parameters too.
I could "reproduce" this behaviour on demo site using the following URL. But i saw, that the label in the URL is not valid. However...the result is the same. :)
I use Piwik 2.14.1
I use Piwik 2.14.1
Please upgrade to Piwik 3 and let us know if you still experience this issue?
Thank you for your reply.
Hm, but i tried to reproduce it on your demo site and it worked. Not good enough?
Is there any bugfix for this, that it is worth to upgrade to the actual version?
I have this problem in production environment (could not reproduce it in development) and there are people working there. The upgrade includes UI changes, so it is not the best option for me.
Yes, this bug was fixed