Test Paginator on the published page with the real data source. Dynamic records, image loading, responsive layout, and fixed headers can all affect the final behavior.
No pagination appears
Confirm that the content source returns more items than the configured Number of posts. Check that the repeated items are inside the same supported grid or list contained by Paginator.
The page count is incorrect
Compare the number of rendered items with the CMS or Feeds result. A source-side limit reduces the number Paginator receives. Also check for empty records or elements that are not part of the repeated-item structure.
Bento Mason leaves gaps
Wait until images have loaded, then change pages again. Check that every item has valid dimensions and that the masonry layout is contained within the Paginator instance.
The page scrolls too far
Adjust the scroll offset to account for a fixed header. Disable Scroll to top if the automatic movement is not useful for that section.
Multiple sections interfere
Keep each grid or list inside its own Paginator. Test the first and last page of every instance and confirm that one navigation bar changes only its own content.
Mobile and accessibility checks
Test the mobile page selector with touch and keyboard input.
Keep previous, next, numbered, and Go controls clearly visible.
Use strong contrast for default, hover, and active states.
Use readable page-count and placeholder text.
Keep entrance animation brief and avoid making it the only indication that content changed.
If the problem remains, email support@stackswork.com with the Paginator version, content source, items-per-page value, public test URL, affected viewport, and a short screen recording if motion or layout is involved.
Related: Paginating grids, Feeds, and Total CMS lists and Configuring navigation, scrolling, animation, and styling.