Skip to content

Loading…

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

Closed
mattab opened this Issue · 1 comment

1 participant

@mattab
Piwik Open Source Analytics member

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
Piwik Open Source Analytics member

(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
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.