Filter: bricks/query/result_start
The bricks/query/result_start filter changes the numeric starting position stored in $query->start. Query Results Summary reads this value for its %start% placeholder.
This filter changes summary metadata only. It does not change the returned items, skip the first item, limit the rendered cards, change the total count, or fetch another page.
Parameters
Section titled “Parameters”$start(int): The current starting result position. Native post, term, and user queries normally calculate one-based positions. The value can be0when no range has been populated, including in provider-backed ACF loops.$query(Bricks\Query): The query instance. Use its public$element_idproperty to scope the filter to a specific loop element.
Example usage
Section titled “Example usage”This example adds one to the starting position reported for a specific loop. It changes only the summary number; the first item still renders.
Replace abc123 with the loop element’s raw Bricks ID, without the brxe- prefix or a #.
add_filter( 'bricks/query/result_start', function( $start, $query ) { if ( $query->element_id === 'abc123' ) { // Adjust the summary's starting position only. return $start + 1; }
return $start;}, 10, 2 );For example, if $start is 1, the summary reports 2. All returned items still render in their original order, and %end% and %total% remain unchanged.
Change the actual results
Section titled “Change the actual results”Use the Query Loop controls for native query limits and offsets, or bricks/query/result to modify fetched results.
For an ACF loop that returns an array, a result filter scoped to the loop element can use array_slice() to skip or limit items. This changes the returned array while preserving the saved ACF entries and the editorial order of the retained items. See the ACF array example.
Was this helpful?
A quick vote and short notes help us improve these docs faster.
Leave a note for us
Please do not include passwords, license keys, or personal data. We store submitted notes to improve the docs.
Thanks for sharing feedback. We're using it to improve these docs.