-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Paginate does not work #603
Comments
What is your Livewire version? |
Sorry I did not fill the version because it's the one shipped with filament. |
Interesting. Can you create a brand new project and see if the issue is there too? I've never hit this. |
I've just create a brand new project and the result is the same. Here is what I have done:
We could imagine the issue comes from the nginx or fpm setup, but even deployed on a bare server, the behaviour is the same. |
I faced the same issues a few days ago, and was thinking about making a pr. The issue here is the 2.6 update of Livewire (which should be installed here), they changed the pagination code to support multiple paginations, they now use an array with the paginations name to handle the page number. Changing the setPage function in this package to include the array, fixed it for me: public function setPage($page)
{
$this->page = $page;
$this->paginators['page'] = $page; // this line here
$this->selected = [];
} |
I'll bump the minimum Livewire version to v2.6 and PR that fix. Thank you. |
Package
filament/filament
Package Version
1.10
Laravel Version
8.61.0
Livewire Version
No response
PHP Version
7.4.16
Bug description
My pagination does not work. The paginator displays the correct amount of pages, but clicking on a page refresh the first one only.
I thought my tables where messed up but the issue is behave the same way on the default user list:
Here is an ouput of telescope showing the last click of the gif: the page 7.
The MySQL query does not seems to get the correct offset.
What may have caused this issue and how can I fix it ?
Steps to reproduce
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: