Search Form Settings
Introduction
The Search Form tab controls how user input is converted into search queries against the Target Form entries.
You define field mappings, optional creator and entry-meta filters, proximity behavior, and how searches are executed.
Configuring Search Form Settings
1. Search Form Mode
Search Form Mode controls whether the Search Form UI is displayed on the front-end.
Disable Search Form
Hide the search form UI and run searches using Initial Load, Search Defaults, and Predefined Filters.
Use this for listing-style pages where users should not be able to change filters manually.
This is useful for automatically generated directories, restricted views, and pre-filtered pages.
2. Filter Mappings
Filter Mappings connect Search Form fields to Target Form fields and build the main query rules.
Filter Match Mode
- Match All Rules (AND): all mapping rules must match.
- Match Any Rule (OR): one or more mapping rules can match.
Field Mapping Rules
Click Add Rule to create a rule that includes:
- Source Field: Search Form input field (or subinput for Name/Address fields).
- Target Field: Target Form field used in query comparisons.
- Operator: Comparison operator based on source field type.
Multiple rules can be combined for advanced query behavior.
If source/target field combinations are invalid, those mappings are skipped from query generation.
If a mapped source field is removed from the Search Form after saving, the mapping is preserved but marked as unavailable until fixed.
For date-based rules, Date source fields are strongly recommended. If you are using select/radio-based date values, ensure values are stored as Y-m-d.
3. Creator Filter Mappings
Creator filters allow Search Form fields to query entry creator data from WordPress.
Creator User ID Field
Map to the creator user ID.
Creator Role Field
Map to the creator role key.
Creator Text Search Field
Map to searchable creator text such as username/display name.
Use in member directories, internal staff listings, and user-generated entry views.
4. Entry Meta Filter Mappings
Map Search Form fields to built-in Gravity Forms entry metadata filters.
Status
Filter by status values.
Entry ID
Filter by exact entry ID.
Date Created (Start) / Date Created (End)
Define a created-date range using operators >= / <=.
Date Updated (Start) / Date Updated (End)
Define an updated-date range using operators >= / <=.
Post ID
Filter by linked WordPress post ID.
Payment Status
Filter entries by payment status values.
Payment Amount
Filter by payment amount using numeric operators.
Transaction ID
Filter by transaction ID values.
A meta filter row is only applied when its mapped Search Form field contains a value.
Leave a row as Not Mapped to disable that filter.
5. Location Data Scope
Location Data Scope controls which geocoded fields from the Target Form are used for proximity and map-based behavior.
Location Source Fields
Select one or more geocoded fields from the Target Form. This is required for map/proximity features.
If no valid location source fields exist, the UI shows a notice and no map/proximity source can be effectively used.
Hide Entries Without Location
Exclude entries missing location data from results.
This is useful for strict location-based listing experiences where every result should have a position.
6. Proximity Search
Proximity Search requires indexed location data. If existing entries are not appearing in results, see Importing Existing Entry Locations.
Proximity search lets visitors find entries within a radius of a selected address/location.
Enable Proximity Search
Turn this on to enable distance-based searching and result-distance calculation.
This setting is disabled until at least one Location Source Field is selected.
Address Field
Select a Search Form text field used as the address input.
It becomes the center point for radius-based searches.
Address Locator Button
Adds a button to capture the visitor’s current location.
Available only when an Address Field is selected.
Address Autocomplete
Enables Google Places autocomplete for address entry.
Autocomplete Countries
Optional country filtering for autocomplete results.
Autocomplete Language
Optional autocomplete language override.
This becomes available when Address Autocomplete is enabled.
Radius Field
Select a Search Form field that provides the search radius value.
Units Field
Select a Search Form field that provides distance units (for example, miles or kilometers).
Radius and units inputs should be configured so the data format matches your front-end query behavior.
7. Search Behavior
Search Behavior determines when searches are executed.
Auto-submit on Filter Change
Enables live search updates when mapped filter values change.
When disabled, users must submit the Search Form manually to run a search.
Enable for directory-style filtering, faceted UX, and AJAX-like immediate updates.
How Search Form Settings Work
Search Form settings define the query contract for the search request. They map frontend input to query logic and then combine that with defaults/predefined filters and proximity constraints.
At runtime, Filter Mappings, Creator Filters, Entry Meta Filters, Location Data Scope, and Proximity Search are evaluated together to produce the final result set.
For most search experiences, Filter Mappings and Proximity Search are the primary building blocks.
Tips for Setup
- Set the Target Form first. Some settings are only available once it is selected.
- Set up Filter Mappings before tuning display or result output.
- For proximity search, select at least one Location Source Field and an Address Field first.
- Use Match All Rules (AND) for strict filtering, and Match Any Rule (OR) for broader matches.
- Enable Auto-submit on Filter Change only when a dynamic search UX is desirable.