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

Actions > Exit/Entry pages Next/Previous links a bit buggy #2022

Closed
mattab opened this issue Jan 15, 2011 · 1 comment
Closed

Actions > Exit/Entry pages Next/Previous links a bit buggy #2022

mattab opened this issue Jan 15, 2011 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jan 15, 2011

the table thinks there are more rows to display but this is not the case. This is because entry/exit reports only show these rows that have an entry or exit, but the table still technically contains all rows

@mattab
Copy link
Member Author

mattab commented Jan 15, 2011

(In [3748]) Fixes #2022

  • Introducing 'priority filters' that can be queued from the Controllers directly, and can remove rows from the DataTable returned from the API.
    This is for example useful for several Controller views that use a same data source, but are interested in a different subset of this dataset. For example, Exit pages, Entry Pages and Page URLs all use the same DataTable, but Exit pages will only display the rows that have Exits / Exit rate. Therefore they must delete other rows in a filter that is applied before the 'Generic filters' that are Sort, Limit, etc.

@mattab mattab added this to the Piwik 1.2 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.
Projects
None yet
Development

No branches or pull requests

1 participant