I finally managed to overcome the issue of Bricks query loops - one root element - with a workaround using the /frontend/render_element to group posts of the same month and add the heading.
Something as simple as that should not take a workaround, PHP to add all the grouping HTML and 10+ hours to avoid all side effects of render_element on an an item that is looped.
Quite hard to maintain and cumbersome, but at least it works for now.
I have to correct myself. This is not possible in combination with WP Grid Builder filtering and looks like the next limitation, that you run into, when circumventing the limitation of the single loopable element.
It needs to be dynamic, automatic and not worse than I the already perfect integration I had in Oxygen.
That’s not a maintainable solution, nor a solution, that supports pagination or filtering.
Update: Okay, JS is a workaround that will do the trick, but I don’t want to hide stuff with JS or CSS and pollute the DOM with irrelevant tags. I want to use PHP to directly create the proper HTML.
The only viable solution I can think of is one query with condtions, which in the worst case need to be implemented fully in PHP instead of the Bricks UI.
second method I wrote is very simple to implement and completely native and fully dynamic and pagination possible because only one loop (you will need couple line of js thats it)
I am pretty sure because I already developed couple similar loops before
The easiest JS solution is reading the date of each post and on each month change add the month divider and the HTML container, that wraps it.
Then you need to make sure that updates are triggered with WP Grid Builder filters and pagination.
