NO BUG: Query ACF repeater data not displaying data from other pages

[timmse]

Hi muz,
Thanks for your report!

This is not a bug. The ACF repeater query type does not currently store a separate “source page ID”. The query dropdown lists loop-capable ACF field definitions; the actual repeater rows are resolved from the current post/loop context (the post/page you’re currently editing).

The solution for pulling the repeater fields from another post or page is incredibly simple:

1. Add an outer Block/Div and enable Use Query Loop.
2. Set that outer query to Posts.
3. Set post type to Pages.
4. Use Include to include only the source page ID.
5. Inside that outer loop, add another Block/Div.
6. Enable Use Query Loop on the inner element.
7. Set the inner query type to your ACF Repeater: ... field.
8. Add your repeater subfield dynamic tags inside the inner loop.

The outer one-item page loop makes the source page the active post context, so the inner ACF repeater loop can read the repeater rows from that page.

If this repeater is meant to be reused site-wide, an ACF Options Page is often the better choice. Then the repeater is not tied to one page’s post context.

For a code-based workaround, you can also override one specific loop with bricks/query/run, which is the documented hook for returning a custom query result. Example:

add_filter( 'bricks/query/run', function( $results, $query_obj ) {
	if ( $query_obj->element_id !== 'abc123' || ! function_exists( 'get_field' ) ) {
		return $results;
	}

	$rows = get_field( 'your_repeater_field_name', 123 );

	return is_array( $rows ) ? $rows : [];
}, 20, 2 );

Replace abc123 with the raw Bricks ID of the repeater loop element, your_repeater_field_name with the ACF field name, and 123 with the source page ID.