Bug
When calling gf_list_entries, pagination, exclude, and include parameters are silently ignored. The API always returns the same first 10 results regardless of current_page or page_size, and total_count reflects unfiltered totals.
Steps to reproduce
- Call
gf_list_entries with form_ids: [129] — returns 10 entries with total_count: 52
- Call again with
paging: { current_page: 2, page_size: 25 } — returns the same 10 entries
- Call with
exclude: [96656, 96653, ...] — returns the same entries including excluded IDs
Root cause
In src/gravity-forms-client.js around line 314, listEntries() spreads all validated params into searchParams:
const searchParams = { ...validated };
But only search, sorting, and paging are JSON-stringified before being passed to the API. The exclude, include, form_ids, and status parameters are passed as raw arrays, which the Gravity Forms REST API silently ignores.
Expected fix
All array/object parameters (exclude, include, form_ids) should be JSON-stringified before being sent as query params, consistent with how search, sorting, and paging are handled.
Workaround
Query the wp_gf_entry and wp_gf_entry_meta tables directly via Metabase SQL.
Bug
When calling
gf_list_entries, pagination,exclude, andincludeparameters are silently ignored. The API always returns the same first 10 results regardless ofcurrent_pageorpage_size, andtotal_countreflects unfiltered totals.Steps to reproduce
gf_list_entrieswithform_ids: [129]— returns 10 entries withtotal_count: 52paging: { current_page: 2, page_size: 25 }— returns the same 10 entriesexclude: [96656, 96653, ...]— returns the same entries including excluded IDsRoot cause
In
src/gravity-forms-client.jsaround line 314,listEntries()spreads all validated params intosearchParams:But only
search,sorting, andpagingare JSON-stringified before being passed to the API. Theexclude,include,form_ids, andstatusparameters are passed as raw arrays, which the Gravity Forms REST API silently ignores.Expected fix
All array/object parameters (
exclude,include,form_ids) should be JSON-stringified before being sent as query params, consistent with howsearch,sorting, andpagingare handled.Workaround
Query the
wp_gf_entryandwp_gf_entry_metatables directly via Metabase SQL.