Pagination Issue – "Previous" Button Appearing on First Page and Affecting Interactions

Attributes
,
1

Hello,

I’m experiencing an issue with pagination across all my collection lists. When I publish my site, the “Previous” button appears on the first page, which it shouldn’t.

Normally, the “Previous” button is supposed to show up starting from the second page, but in my case, it’s visible from the first page as well.

Additionally, this issue removes or disables my interactions on the second page, which is affecting the user experience.

I’m not sure if this is a Finsweet, or possibly something related to my pagination settings or custom attributes.

Could you please help me investigate this behavior?

Thanks in advance for your support!

Best regards,

Site URL

Required: Please provide a staging/production URL where we can see the issue

Expected Behavior

I don’t want the previous pagination button to appear on the first page.

Actual Behavior

he ‘Previous’ button remains visible on the first page, but the interaction doesn’t function on the second page

Video/Screenshots

Capture d’écran 2025-06-20 à 09.00.29
Capture d’écran 2025-06-20 à 09.00.292636×794 189 KB

2

Hey @mlaurent! You can now control the disabled state of the next and previous buttons when no more pages are available by adding the combo class is-list-pagination-disabled to the previous and next buttons.

Regarding the interactions, you should add the fs-list-resetix = true attribute to your list element; this will reset the interaction engine.

Please note that all interactions that have an Initial State will be restored to it, use with caution to avoid unexpected UX behaviors. You can simulate this initial state using the effects panel.