WAIT: Post Widget: Two pagination bugs — filter state lost + last page error

Browser: Chrome 110
OS: macOS

Bricks Version: 2.3.2
WordPress Version: 6.9.4


Bug 1: Pagination breaks when a category filter tab is active

Steps to reproduce

  1. Add a Post element to the page
  2. Set the post type to Posts
  3. Set posts per page to 6
  4. Under Filters, add Categories
  5. Enable Pagination
  6. On the frontend, click any category tab
  7. Click to go to page 2

Expected behavior
Page 2 should continue showing posts filtered by the selected category tab.

Actual behavior
Page 2 loses the active filter and falls back to showing all posts — the pagination links do not carry the category context forward.


Bug 2: Last page shows “Oops, no page found” error with odd post counts

Steps to reproduce

  1. Add a Post element to the page
  2. Set the post type to Posts
  3. Set posts per page to 6
  4. Keep Filters disabled
  5. Enable Pagination
  6. Have a total post count that isn’t evenly divisible by 6 (e.g. 23 posts → 4 pages)
  7. On the frontend, navigate to the last page (page 4)

Expected behavior
Page 4 should display the remaining 5 posts (posts 19–23).

Actual behavior
Page 4 shows an “Oops, no page found” error — no posts are rendered despite valid posts existing for that page.

Additional context
The widget correctly shows 4 pages in the pagination UI, but the query on the last page fails to fetch the remainder. This suggests the offset or query calculation on the final page is going out of bounds when the total post count is not a clean multiple of the per-page value.


Both issues are consistently reproducible.

Hi Stuti,
Thanks so much for your report!

  1. The posts element filter isn’t actually a “real” filter. It’s an isotope filter that filters the elements currently available on the page. It’s not intended to be used alongside the pagination. If you want a “real” filter, you can use one of the dedicated filter elements, which work entirely differently.

  2. Please try to enable “Disable query merge” and/or “Is main query”.

Best regards,
timmse

Hi timmse,
Thanks for the quick response!

Regarding Bug 1, that makes sense — I wasn’t aware the isotope filter wasn’t intended for use with pagination. I’ll switch to the dedicated filter elements instead. On a side note, I do find it a bit difficult to locate things in the Bricks documentation in general — better searchability or navigation there would be really helpful.

For Bug 2, I’m not sure if your suggestions were meant to address it or just Bug 1. To clarify — this one has no filters involved at all, just a plain Post element with 6 posts per page and pagination enabled. When the total post count isn’t a multiple of 6 (e.g. 23 posts), the pagination shows 4 pages correctly, but navigating to page 4 throws an “Oops, no page found” error instead of showing the remaining posts.

I did try enabling both “Disable query merge” and “Is main query” but unfortunately neither resolved the issue. The last page error persists.

Could you look into this further? Thanks!

We’re already working on it :wink: Check the preview of the Academy revamp:

I can’t say why it isn’t working for you. Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

1 Like

Thank you so much for looking into this! And it’s really great to hear that the Academy revamp is already in the works — that’s honestly exciting news :star_struck: , looking forward to it!

I’ll get the login credentials sorted and send them over shortly.