Deprecated and renamed hooks

Every GravityView hook that has been renamed is listed here with the name to use now. If a deprecation notice appeared in your WordPress dashboard, find the hook it named in the tables below.

Looking up a hook #

Every hook name in the tables below links to its page on the GravityKit developer docs, where you get the parameters, the version it shipped in, the file and line it fires from, and a working example. That is the reference to keep open while you migrate.

If you write code with an AI assistant, connect the GravityKit Developer Docs MCP instead of pasting hook names into it. Your assistant then looks up the real signature rather than guessing at one, which matters here: a model trained before these renames will confidently hand you the deprecated name. It is free, hosted, and needs no API key.

claude mcp add --transport http gravitykit-docs https://mcp.gravitykit.dev/

claude mcp add --transport http gravitykit-docs https://mcp.gravitykit.dev/

Cursor, VS Code and other MCP clients take the same server as a configuration entry. Setup for every client is here.

Why you are seeing a deprecation notice #

GravityView shows the notice only when WP_DEBUG is enabled, so it reaches developers rather than site owners. The notice names the hook, the file and line where your code hooks it, and the replacement:

The gravityview_fe_search_criteria hook used in themes/your-theme/functions.php:120 has been deprecated. Use gravityview/view/query instead.

Code inside GravityKit plugins is ignored, so a notice always points at code you or another developer control.

How the names changed #

Hook names have been through three generations. Which one you are looking at usually tells you how old a snippet is:

• gravityview_entry_class. Underscores throughout, the original 1.x style.
• gravityview/template/list/entry/class. Slash-separated, introduced with the 2.0 rewrite.
• gk/gravityview/search/datepicker/format. Prefixed with gk/, the current convention shared across GravityKit products.

Two vocabulary changes also happened in 2.14: blacklist became blocklist and whitelist became allowlist, in both hook names and method names.

Renamed hooks #

Each row says whether the hook is a filter or an action, so you know whether to reach for add_filter() or add_action(), and the version that deprecated the old name. Both names link to their reference page.

Search Bar

Templates and layout

The List layout also fires a before and after action inside each entry, once per zone:

Fields

Edit Entry

Delete Entry

Widgets

Views and settings

Hooks that need more than a rename #

Four cases where swapping the name is not enough.

gravityview_entry_class has three replacements

gravityview_entry_class applied to every layout. It was replaced by one hook per layout, so pick the one matching the layout your View uses, or add all three:

• gravityview/template/table/entry/class for the Table layout
• gravityview/template/list/entry/class for the List layout
• gravityview/template/layout-builder/entry/class for the Layout Builder layout

The replacements take $class and a \GV\Template_Context object, where the old hook took $class, the entry array and a GravityView_View object.

Two hooks were renamed twice

If you follow the replacement named in the dashboard notice for these, you land on a name that is itself deprecated. Go straight to the final name:

• gravityview/search/operator_whitelist → gravityview/search/operator_allowlist (2.14) → gk/gravityview/search/operators/allowed (2.55)
• gravityview/search/searchable_fields/whitelist → gravityview/search/searchable_fields/allowlist (2.14) → gk/gravityview/search/searchable-fields/allowed (2.55)

Field value hooks collapsed into one

Three separate hooks now share a single replacement, gravityview/template/field/{$field->type}/output:

• gravityview_field_entry_value
• gravityview_field_entry_value_{$field->type}
• gravityview_field_entry_value_{$field->type}_pre_link

To change a field’s value rather than its markup, gravityview/field_output/context/{$tag} is usually the better hook. To change the finished HTML, use gravityview/field_output/html.

Hooks with a variable in the name

Some replacements contain a placeholder. Substitute the real value:

• gravityview/get_users/{$context} takes change_entry_creator or search_widget, so the full names are gravityview/get_users/change_entry_creator and gravityview/get_users/search_widget.
• gravityview/template/field/{$field->type}/output takes a Gravity Forms field type, for example gravityview/template/field/text/output.

Renamed methods #

Renamed in 2.14 alongside the hooks, when blacklist became blocklist throughout. The class never changes, only the method name. The old methods still work and call through to the new ones.

Migrating a hook #

1. Find the old name in the tables above and note whether it is a filter or an action.
2. Open the replacement’s page from the link in that row. Several replacements pass a \GV\Template_Context object where the old hook passed separate arrays, so the parameters usually change.
3. Change the hook name and adjust the callback to the new parameters.
4. Reload a page that uses the View. The notice clears once nothing hooks the old name.

Related #

• GravityKit Developer Docs MCP, for looking hooks up from your AI assistant
• GravityKit developer docs: every GravityView filter and action
• Where to put code samples
• GravityView CSS guide