Scope of filters not limited to the "active" query loop

[SteveRyan-ASU]

When testing this plugin on a page with multiple query loops, the filtering was applied to all of the loops on the page, not just the specific query loop that contained the filter blocks. This was the case with both included filter blocks - the taxonomy term block and the post type block.

The use case I was attempting to build was to display the first X number of posts from a post type in a unfilterable format at the top of a page. Further down, starting with the X offset, I wanted to create a filterable "archive" for the remaining posts in the collection.

[roborourke]

@SteveRyan-ASU this could be if your query loops have ended up with the same queryId somehow. Core really needs to prevent that. I've worked around it in our https://github.com/humanmade/hm-query-loop plugin but that's the main reason I can see for this behaviour.

[roborourke]

Found the mechanism for this, and it's real — leaving this open and tracking the cause in #62.

Filtering is correctly scoped when two loops have different queryId attributes. On WordPress 6.8.8 and 7.0.4, with a taxonomy filter in the first of two loops (ids 28 and 29), ?query-28-category=alpha narrowed the first loop to the two Alpha posts and left the second showing all four.

But two loops that share a queryId are both narrowed by the one control:

URL	Loop 1 (has the filter)	Loop 2 (no filter)
/repro-dup/	all 4 posts	all 4 posts
/repro-dup/?query-7-category=alpha	Alpha One, Alpha Two	Alpha One, Alpha Two

That is exactly what you described, and duplicating a query loop block in the editor is how you get there: duplication copies queryId along with every other attribute (WordPress/gutenberg#55823, still open upstream; core's own enhanced pagination has the same problem). Building "the same loop again, with an offset" by duplicating the first one is the natural way to do what you were after, which fits.

Two workarounds until the plugin defends itself:

• Give each loop a distinct queryId — edit the block markup in the code editor (Options → Code editor) and change "queryId":N on one of them to any other integer. Filters then apply only to the loop that holds them.
• Or build the second loop by inserting a fresh Query Loop block rather than duplicating the first.

#62 covers what the plugin should do about it — at minimum warn instead of silently filtering a loop that has no filter in it.

---

Generated by Claude Code