Problem: {query_loop_index:parentLoop} in triple-nested ACF repeater query — resolves to inner loop instead?
I would like to request a native way to reference a specific parent loop index in deeply nested query loops.
Context
I am building a recipe template with Bricks 2.3.1 + ACF Pro using nested repeaters:
-
Loop 1:
recipe_steps(step loop) -
Loop 2: components inside each step
-
Loop 3: ingredient rows inside components
Each ingredient row has show_at_step and should only render when it matches the current step index (1-based).
Current limitation
In Results Filter / dynamic data, {query_loop_index} always returns the current loop index (as documented).
There is currently no native way to resolve the index of a specific parent loop by ID in deeper nesting.
So in a 3-level structure, filtering Loop 3 by Loop 1 index is not possible natively.
Current workaround
I solved this with custom PHP (bricks/query/loop_object + bricks/query/result) and it works, but this feels like a common visual-builder use case that should be possible without code.
Request
Please add a native dynamic tag / syntax to access parent loop indexes explicitly, for example:
-
{query_loop_index:parent}(direct parent) -
{query_loop_index:ancestor:2}(2 levels up) -
or
{query_loop_index:loop_id}(specific loop element ID)
Any equivalent implementation would help.
Why this matters
-
Enables advanced conditional filtering in nested repeaters without PHP
-
Reduces custom code for common content structures (recipes, lessons, timelines, grouped FAQs)
-
Improves maintainability for no-code/low-code workflows
Thanks for considering this. I can provide a minimal reproducible structure if needed.