Not sure if this is a bug or an issue with what I’ve done.
I created an archive template for standard posts, added a query loop and toggled on “main query”. I added a button, tag type “button”, with an interaction of “click”, “load more (query loop)” and “main query”. The button did nothing. I removed “main query” from the interaction and left it as default, nothing. Finally I changed the query in the drop down to “Post loop” explicitly, which fixed the issue.
I have two other loop queries on the template, neither are set as main queries.
The number of posts per page matches the WordPress settings.
Shouldn’t the button work without explicitly choosing which loop to use in the interaction settings?
thank you for your report. I was able to replicate the issue and I’ve added it to the bug tracker. As you already figured out, you should select the correct loop item. It’s because JS does not know which query is “main” one.
Just confirming that this does indeed seem to be fixed. I did notice however that the “is main query” toggle needs to be turned on in the query for it to work. I’m assuming this is by design?
Without indicating which one is the main query, Bricks doesn’t know which query you are trying to load more. (Imagine Bricks has the flexibility to let users add multiple queries in a template)
