@julienmoumne opened this issue on April 15th 2013

When specifying both filter_limit and filter_sort_column, filter_limit is broken.

In the following example, filter_limit is set to 5 but 9 results are returned :http://demo.piwik.org/index.php?module=API&method=API.getRowEvolution&idSite=7&period=day&date=previous4&apiModule=Goals&apiAction=getDaysToConversion&filter_limit=5&filter_sort_column=nb_conversions

However, it works if filter_sort_column is not specified as in : http://demo.piwik.org/index.php?module=API&method=API.getRowEvolution&idSite=7&period=day&date=previous4&apiModule=Goals&apiAction=getDaysToConversion&filter_limit=5

@diosmosis commented on April 16th 2013

Hi Julien, can I ask is your use case for using filter_limit doing multi row evolution w/o specifying labels? I think filter_limit has no meaning when labels are specified since the labels are what determine how many results are returned.

@mattab commented on April 16th 2013

it will be only when &labels is not specified, like you say it does not make sense to specify filter_limit and labels.

@diosmosis commented on April 17th 2013

In c91a60342fe0e7a52e554ae9da8e78e20c759fd3: Fixes #3897, make sure filter_limit limits the number of labels returned when no labels are specified with multi-row evolution and make sure it has no effect in all other row evolution cases.

This issue was closed on April 17th 2013
Powered by GitHub Issue Mirror