Hello, I am having an issue with pagination. My backend is Supabase and it is paginated to 10 records at a time in the frontend. The table is bound to the highest level of the array. On page load the table shows about 10, then I click the arrow and the next table show less, and I click again and it shows less until no records are displayed. When I click back in the paginator it shows a full table, so I’m guessing it’s fetching all the data but not displaying it for some reason.
In the second picture is looks like the bound collection isn’t pulling all the records. Not sure why, the collection displays 237 items, but seems to be the part of the problem. Thanks for the help!
SOLUTION: The filter on the bound table collection seemed to be slowing things down. The filter as configured should narrow the collection down to about 175 items. When I removed it from the bound table collection and added it as a front end filter to the collection, the pagination started working.
I’m having weird issues too, and I didn’t so far … See the pics below where the paginator element is not working at all (using Supabase, binding my collection to the whole collection, binding the paginator element to the right collection …) :
→ some records are missing, it’s not in the right order (asc. based on the name), the last page is empty (but gets filled when going back to the pre-last one and then to the last one) … Really weird bugs and I don’t know how to deal with it
Yes I also observed two “problematic” topics with weweb pagination x Supabase :
It’s not possible to link pagination to a filtered “collection list” of items, which is painful. Let say I have 100 records (10 page of 10 records) in the global data collection, if the “collection list” filters to keep only 20 items, I’ll still have 10 pages in pagination but the 8 last ones are empty. The only workaround to this has been to filter in backend but that’s not perfect
In some occasions, pagination did not work if explored “out of order”. If i look at page 1 then 2 then … until 10, the 10th page will have items, but if i directly skip to the 10th I sometimes don’t see anything !
EDIT : after removing any filter and sort conditions on the element “collection list”, and putting them directly on the collection data, it seems that it’s now working (I still have issues with the paginator on the collection I csv imported, but I think/hope it’s linked to the text issues of the records).
I wasn’t aware that setting filters on both could make this kind of mistakes ! Always good to know
