Table Widget - extremePaginationLinks and queryStringIdentifier not working
As per screenshots - I've tried setting the queryStringIdentifier and extremePaginationLinks on a table widget but it doesn't seem to work.
I'm still getting
?page=2
in the URL and no extra pagination links 😢
Is this a bug or am I maybe expecting too much of the widgets? If anyone has any tips on how I could get this working I'd be very grateful.
2 Replies
Updated post as I didn't realise screenshots of code were not allowed, apologies.
I've tested the
queryStringIdentifier
on another page and it works fine. It feels both of these issues (query string and normal pagination) is only an issue for Widgets. I can work around this for now but does anyone know if there's a plan to get custom pagination queries on widgets in future? I would happily work on a PR for it myself but I'm still fairly new to Filament and don't really know where to begin.Same problem here (https://discord.com/channels/883083792112300104/1260230838516187167) but I didn't found a solution yet.
I found a solution. Make a custom BaseTableWidget and override the
paginateTableQuery()
by copying the base method from the Filament\Tables\Concerns\CanPaginateRecords
trait :
Then, in your widget extends it, add ->extremePaginationLinks()
to your table and be sure the widget is large enough to allow the pagination to be displayed.