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

filter only applies to first queried site when date-range is used #2530

Closed
cloph opened this issue Jun 30, 2011 · 1 comment
Closed

filter only applies to first queried site when date-range is used #2530

cloph opened this issue Jun 30, 2011 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@cloph
Copy link

cloph commented Jun 30, 2011

A filter applied to the label of the outlinks action parameter is only applied to the first subsite, not to the other ones that are queried at the same time and when a date-range is used.

Works:
Only one site, date range

?module=API&method=Actions.getOutlinks&idSite=2&period=day&date=previous7&filter_column=label&filter_pattern=download&format=xml

Works:
multiple sites, single date

?module=API&method=Actions.getOutlinks&idSite=all&period=day&date=yesterday&filter_column=label&filter_pattern=download&format=xml

Does _not_ work:
multiple sites, date-range

?module=API&method=Actions.getOutlinks&idSite=all&period=day&date=previous7&filter_column=label&filter_pattern=download

result is that the output is filtered for the first site only. The other sites return the results as if the filter was not specified. (No difference when using filter_column_recursive and filter_pattern_recursive instead)
Keywords: actions api, filter, multiple sites, date-range

@mattab
Copy link
Member

mattab commented Sep 21, 2011

(In [5200]) Fixes #2530 by removing wrong optimization causing code to fail, thanks for the bug report cloph

@cloph cloph added this to the 1.6 Piwik 1.6 milestone Jul 8, 2014
This issue was closed.
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. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

2 participants