Pagination must be reset after new filter

[sazary]

Hi
these are the steps to reproduce this bug:

1. go to page n >= 2
2. change a filter criteria, so that the resulting data comes in less pages than n. for example go to page 5, then search for something that has less than 5 pages of data. then table doesn't show anything, but it must show.

how to fix the bug:
reset pagination to page 1 after every change in filters.

[Zizzamia]

Are you using #ngTasty version 0.5.0 ? This looks an old bug already fix few months ago.

[sazary]

yes it is 0.5.0

[Zizzamia]

What table are we talking about:
Table client side

<div tasty-table bind-resource="resource"> ... </div>

Table server side

<div tasty-table bind-resource-callback="getResource" 
bind-init="init" bind-filters="filterBy"> ... </div>

I try to replicate the error on the docs, but was not possible.

[sazary]

I'm talking about server side one. follow these steps to reproduce the bug:

1. go to this page.
2. search for "s".
3. go to page 3.
4. now search for "bar".
5. note that number of pages in pagination bar reduces to one page, but no item is shown in the table. also note that in the API URL, the page requested is page=3.
6. now click on page one in the pagination bar. items appear.
   I hope that this helps.

[Zizzamia]

#ThankYou @sazary to report this issue, was really helpful!
In the next release will be out this fix.

[sazary]

Thank you for fixing it!

[thesilverbadger]

I'm not sure that this has been fixed, as we're running into the same issue (using 0.5.5), and I can repro on the Table with reload callback page.

1. Click Page 5
2. Enter "cup" in filters by name.
3. Click Search.

The params string doesn't reset the page to 0, instead leaves it at
[sort-by=name&sort-order=dsc&page=5&count=5&name=cup]

I would expect this to reset the page to 0 (as effectively the user is starting from scratch).

[Zizzamia]

Hey @thesilverbadger your problem was fix in the #142 issue.
And if you update #ngTasty to the version 0.5.6 you will get the fix.
Please let me know if you still have problem.

[javmg]

Hi there,

I think the issue may still be present in the latest version 0.5.8.

We can test it this way:

1. Navigate to http://zizzamia.com/ng-tasty/directive/table-server-side/complete
2. Clear the "r" from the filters (by name)
3. Click on page number 5
4. Introduce "cup" in the filters (by name)

There is a result but it is not shown (I am attaching a snapshot of the problem). If we click on the page number 1 everything would be fine.

Regards,

Javi

[Zizzamia]

Hi @javi-more-garc thanks to report the bug,
the docs were not update with the latest version on ngTasty,
http://zizzamia.com/ng-tasty/directive/table-server-side/complete

Just fix that :-)

[javmg]

Hi,

thank you for your response.

My implementation does not rely on a front-end filter but rather performs a search and the server returns all results sorted/ filtered.

The behavior is analogous: say I search and get 15 results. I click on the second page and search again using a more restrictive filter. The server returns 6 results this time but there are no rows shown even when I can see there is a page:

Even the footer is right: "Page 1 of 1, of 6 entries" but there are no rows. If I click on the page (1) everything is fine (i.e. rows are displayed)

Is there any way to sort of reset everything (current page, sorting..) so that the new results from a search are displayed as if it was the first time?

Thank you,

Javier

[Zizzamia]

@javi-more-garc can you please open a new issue about this error. :-)
Thanks