Bricks Version: 1.5 Browser: Versie 104.0.5112.105 (Officiële build) (64-bits) OS: Google Chrome OS / Windows 10
I have a archive page with a “brand” card quering a custom post type built with Metabox.
When I set the scroll on infinite and the order on random I’m getting duplicate content. I would guess the system would be smart enough to know which content has already been loaded. Turning the random mode of fixes the problem. However I really do wish to show in random order, a same kind of issue seems to exist when switching to pagination.
This issue hasn’t been fixed in version 1.6.2. I’ve just encountered the exact same issue. See this screencast (the grid of restaurants is a query loop, configured as follows):
Hi Eric,
No work has been done on this report either, as we have not received any feedback. That is why the title has been set to “WAIT” for 5 months.
I tested it again with Bricks 1.7 and can confirm the issue still exists. However, this is not a Bricks problem per se, but a general problem that occurs with the “rand” order (you will find countless hits if you google for it).
As far as I can see, however, there also seems to be a solution to this. I’ve added it to the list.
