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
Pagination doesn't work after search #252
Comments
I'm not sure if it's a bug. But I haven't encountered this behavior. Last time I checked, everything seems fine to me. Are you using vue-router? If so, that might be the problem. |
Yes, I'm using vue-router but error occurs without changing route |
Try to inspect the search result that returned from the server and if the returned result is correct or not. The only thing I can think of is that there's a problem with the returned result. You can also clone this repo, then run |
I'm having the same problem, when I filter somehow that the page is not needed and then when it comes back with an amount that it's possible to paginate it out of that problem. Could it be some other library or the vue itself? Here I gave an npm update and this problem occurred. |
This sudden change in |
This has been fixed in v1.6.6 of Vuetable-2. See the release note here |
Hi. Got the same issue using v1.7.6 had to onPaginationData(paginationData) {
if (this.$refs.paginationTop)
this.$refs.paginationTop.setPaginationData(paginationData);
if (this.$refs.paginationInfoTop)
this.$refs.paginationInfoTop.setPaginationData(paginationData);
if (this.$refs.pagination)
this.$refs.pagination.setPaginationData(paginationData);
if (this.$refs.paginationInfo)
this.$refs.paginationInfo.setPaginationData(paginationData);
}, |
Hi, when i'm searching and results are less than per page, pagination component being removed from page and then when i'm searching again with empty string it throws error
because it can't find
this.$refs.pagination
e because it has been removed after first search.Tried to wrap
with another div and it works.
is it a bug?
The text was updated successfully, but these errors were encountered: