Bricks Version: 1.6 Browser: Chrome 90 OS: Windows 10
When having 2 (or maybe more) query loops on the same page and using the pagination element with one of them (with or without ajax) the query loop without the pagination element will not be displayed when a user was on another page (by using the navigation) other than the first and then refreshes the page.
So for example if you have a section with query loop and pagination element containing something like 6 posts (let’s say you display only one post in that section) and go to the second page (to see the second post) and refresh after that, the other section/container with query loop will not be shown. It does make sense because your actually refreshing while on “page 2”.
I think this can’t be solved or is too complicated (but i really don’t know). It is normally not a big roblem, but for someone refreshing the page (which happens mostly when creating or changing the page ) it can be handy to know.
This still appears to be the case when using the Ajax option. If you advance to the 2nd, 3rd, 4th page, and so on, the pagination doesn’t show what page you’re on, but does, in fact, load the correct sequence of posts per the post count selected in the loop. It would be nice if this were fixed…
Based on your description, seems like your AJAX pagination is working but the “current” indicator is not. Can you please create a new thread and describe it + provide a link for us to check?
So sorry for no replying this in 2022. However, seems like “Disable Query merge” for those queries not needed for the pagination function should solved your issue now in Bricks.
No problem. I don’t remember what i did at the time, but i checked a website which i think had this is and it is working. I see that “disable query merge” is turned on in one loop.