GravityView - Display Gravity Forms Entries on Your Websites v3.7.0 Nulled + All Addons

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.7.0 Nulled + All Addons
= 3.7.0 on October 8, 2026 =

This release makes "Search Everything" and sorting use what fields display rather than what they store, fixes several security issues around entry visibility and exports (we recommend updating), and resolves many issues with embedded Views, search, multi-page Edit Entry, and combined forms.

#### Improved
* Broader "Search Everything" matching that covers what fields display, not just what they store:
- Names of users, posts, entries, and database table rows that Dynamic Lookup, GP Populate Anything, and GP Nested Forms fields store by ID;
- Labels of choice fields, such as Drop Down and Checkboxes;
- Fields inside Repeater fields.
* Sorting by fields that store the ID of a user, post, entry, or database table row, which now orders entries by the displayed name, including in Views that combine forms with the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension.

#### Security
* Views embedded with a `{user:...}` merge tag in their search (such as `search_value="{user:ID}"`) showed every entry to logged-out visitors instead of none.
* The Entry and Entry Field blocks, the `[gventry]` and `[gvfield]` shortcodes, entry embeds (oEmbed), and the REST API's single entry route could display entries that the View's filters exclude, such as entries hidden by Advanced Filtering conditions or by the "Show only entries created by the currently logged-in user" setting.
* Entries not listed on a page could be opened in its lightbox when the page also contained an escaped `[[gravityview]]` shortcode or a secured View embedded without its secret.
* The Single Entry page heading of a View embedded in a reusable block could show the title of an entry the visitor wasn't allowed to view.
* Search Bar fields restricted to logged-in users could still filter results for logged-out visitors.
* A GravityView Search widget left in the WordPress Inactive Widgets area still allowed visitors to search by its fields.
* Some values in CSV and TSV exports, including bulk action exports and the attachments manifest, could run as spreadsheet formulas when the file was opened in a spreadsheet application.

#### Fixed
* Pages with a Search Bar widget loaded more slowly after the GravityView 3.5.0 update, increasingly so with each search field, form field, and user on the site.
* Custom CSS that arranged List or Layout Builder entries into columns with the Legacy theme, such as the grid CSS from our documentation, displayed every entry in a single column after the GravityView 3.5.0 update.
* Entry links set to open in a lightbox, such as `[gv_entry_link lightbox="true"]`, opened a full page instead in [DataTables](https://www.gravitykit.com/products/datatables/) 3.14.0 and later and in Views that refresh results without reloading the page.
* Single Entry Title issues:
- Single Entry pages and the entry lightbox had an empty title, and the Breadcrumbs block showed "(no title)", when the Single Entry Title setting was empty (the default) or its merge tags had no value for the entry — Single Entry pages now fall back to the page's title;
- Single Entry pages of an embedded View with a Single Entry Slug showed the page's title instead of the Single Entry Title, and GravityView Social Sharing & SEO gave them the page's SEO title and the wrong canonical URL;
- Views embedded with a merge tag in their search (such as `search_value="{user:ID}"`) showed the page's title instead of the Single Entry Title and couldn't open entries in a lightbox.
* Issues on pages that display more than one View or entry embed:
- When the same View was embedded more than once, an embed could show another embed's search, page size, or other shortcode settings, lose its widgets, or refuse to open its own entries in a lightbox;
- When the same View was embedded more than once, its Single Entry pages displayed the entry once per embed;
- A View lost its Search Bar widget, pagination, and other widgets when it followed an Entry block or `[gventry]` shortcode showing a Map View entry, or an entry displayed through a theme's legacy single entry template;
- A View embedded in another View's field, such as a Custom Content field, pushed the parent View's remaining entries outside the View.
* Issues in Views that combine forms using the Multiple Forms extension:
- With entry caching enabled, Views combining many forms through joins or unions could show another View's entries and ignore searches;
- With entry caching disabled, a page showing two Views of the same form, one of which combined other forms, could display the first View's entries in the second View;
- Sorting by a field that one of the combined forms lacks ordered that form's entries by entry ID and applied the second sort field as the first;
- The Entry and Entry Field blocks and the `[gventry]` and `[gvfield]` shortcodes showed nothing for entries from a form combined through a union.
* Issues with the First and Last entry options:
- The Entry Link block and `[gv_entry_link]` shortcode set to First or Last could link to an entry from a different View on the same page, and Last stopped at the end of the View's first page;
- The Entry and Entry Field blocks and the `[gventry]` and `[gvfield]` shortcodes showed the first entry when set to Last, and both First and Last shifted with the View's current page.
* Search Bar widget issues:
- Chained Selects fields didn't appear, and searching by them listed every entry;
- Dropdowns didn't show the Drop Down field's Placeholder as their first option;
- With "Search Everything" limited to visible fields, searching by a field the View didn't display (including through a GravityView Search widget) returned every entry.
* "Search Everything" issues:
- Required (`+`) words matched an entry only when they all appeared in the same field;
- In Views with joined forms, rows containing an excluded (`-`) word in one of the forms were still shown;
- In Views that combine entries from several forms, an excluded (`-`) word returned no entries, and limiting the search to visible fields didn't apply to the added forms;
- When limited to visible fields, an excluded (`-`) word still filtered out entries that contained it in a hidden field, and fields inside a visible Repeater field weren't searched;
- `%` and `_` acted as wildcards, matching any text or any single character, instead of being treated as plain characters.
* Search issues with fields that store IDs, such as Dynamic Lookup, GP Populate Anything, and GP Nested Forms fields:
- Searching by the displayed name found nothing because it was compared with the stored ID;
- Picking a Dynamic Lookup value from a Search Bar dropdown, radio button, or link also matched entries whose stored IDs contained it (for example, `7` also matched `78`) — choices now match exactly, and Lookups that store several IDs match any one of them;
- Searching a Dynamic Lookup field that uses the Checkbox input or a multi-select Select input found no entries.
* With "Allow searching beyond the start and end date range" enabled, Single Entry pages could show entries outside the View's date range when the page address included a date search.
* Issues with multi-page forms in Edit Entry:
- Next and Previous saved the entry but stayed on the same page when the button text didn't match GravityView's translation for the user, such as for users in another language or when the View's Next or Previous text was customized;
- Page links, such as those added by GP Multi-Page Navigation, opened the next page instead of the one clicked;
- When a submission failed validation, a different page opened and the error stayed hidden on the page that had it;
- Fields on pages after the first were saved without validation (for example, an Email field with an invalid address), including through GP Multi-Page Navigation's page links.
* Edit Entry flagged an unchanged Date or Time field with No Duplicates enabled as a duplicate, preventing the entry from being saved.
* Links to specific View editor tabs, such as "Add fields to Single Entry" in the notice shown when a layout hasn't been configured, opened the wrong tab.
* Issues with merge tag modifiers added by GravityView, which modified a field's stored value instead of its displayed value:
- Text modifiers on Radio, Drop Down, and other choice fields changed the choice's value instead of its label (for a "By Phone" choice with the value `phone`, `:strtoupper` showed `PHONE` instead of `BY PHONE`);
- Some modifiers removed HTML escaping from text fields;
- `:format:Y-m-d` on a Date field showed the field's display format (such as `03/09/2026`) when the stored date was already in the requested format;
- Gravity Forms modifiers in the same merge tag, such as `{Contact Method:1:value,strtoupper}`, were ignored.

#### Developer Updates
* First and Last lookups in `[gventry]`, `[gvfield]`, `[gv_entry_link]`, and the Entry blocks now run the `gravityview/view/entries` filter, which receives the looked-up position as a new fourth argument (`null` for the View's page), and return nothing if a callback removes the boundary entry instead of moving on to the next one.
* Added `gk/gravityview/view/boundary-entry/run-entries-filter` filter to stop First and Last lookups from running the `gravityview/view/entries` filter.
* Added `gk/gravityview/edit-entry/redirect` filter to change where Edit Entry redirects users after an update.
* Added `gk/gravityview/fields/gravityview-view/pre-render` filter to replace a View field's output before it renders the embedded View.
* Added `gk/gravityview/shortcode/is-reembedded` filter to let a View rendered inside another View's page show its Single Entry pages and widgets.
* Added `View::get_entry()`, which returns an entry only if the View lists it, and `View::lists_entry()`, which checks an already-loaded entry against the View's filters and is now used by `GVCommon::check_entry_display()`.
* `GVCommon::check_entry_display()` now allows an Embed Only View's entries on pages that belong to a different View, while the View's own URL stays closed.
* `gravityview()->request->is_entry()` called without a form ID now looks up custom entry slugs only in the form of the requested View.
* Items added through the `gk/gravityview/search/searchable-fields/allowed` filter can set `is_search_key` to `true` to keep a non-field search key, such as a map area, searchable when "Search Everything" is limited to visible fields.
* The REST API's single entry route now returns 404 for every entry the View doesn't show, including unapproved entries and entries from other forms, which previously returned 403.
* Fixed a PHP warning logged on every page after the first when editing multi-page forms in Edit Entry.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.36.0.

= 3.6.0 on October 1, 2026 =

This update makes removing files in Edit Entry safer, includes security fixes, and resolves issues with Edit Entry, Populate Anything fields, search, and View layouts. We recommend updating.

**Note: GravityView now requires Gravity Forms 2.9.4 or newer.**

#### Improved
* File removal in Edit Entry, which now takes effect only after clicking Update (leaving the page without updating keeps the files).

#### Security
* Improved security when deleting uploaded files in Edit Entry.
* Fixed a data disclosure issue in Edit Entry, limited to users already allowed to edit the entry.

#### Fixed
* The "Hide View data until search is performed" setting did not hide entries from the REST API, CSV and TSV exports, or `[gravityview detail]` counts, and blank searches or searches on fields the View did not offer still showed entries.
* Issues with choice fields populated by Populate Anything:
- Saving an entry in Edit Entry changed or erased choices beyond the first 501, the default maximum Populate Anything loads;
- Inline editing with GravityEdit did not offer saved choices that were not among the loaded choices, so saving erased them;
- Merge tags used outside Custom Content fields showed the stored value instead of the label;
- Custom entry slugs built from these fields switched between the stored value and the label (they now always use the label).
* Issues in Edit Entry:
- Conditional logic restored the wrong value to a dynamically populated field whose parameter name matched an entry property, such as `ip`;
- Calculation fields stopped updating after the first save when the entry had no stored value for them;
- With Gravity Forms 3.1.2, files uploaded to a multi-file field were rejected when the form was resubmitted after a validation error;
- Multi-file upload errors showed "Array" instead of the message for each file.
* Gravity Flow assignees could not delete uploaded files on User Input steps while GravityView was active.
* DataTables column filters had no effect after updating to GravityView 3.5.0.
* View settings added by add-ons, such as GravityMath's Calculation Row Background, went missing from the View editor in GravityView 3.0.
* Search Bar widget issues:
- A large gap appeared between each search field and the Search button in the Horizontal layout on Views not using the Vantage theme;
- Labels for radio, checkbox, date, date range, and number range fields ignored the theme's label styling and appeared at body text size;
- Searches that did not specify a search mode ignored the Search Mode saved on the View and matched any field.
* Layout issues:
- List and Layout Builder Views set to more than one column showed every entry in the first column;
- Entries in Vantage Layout Builder Views lost the space between them;
- Vantage Table Views grew wider than the page when a field held long text instead of wrapping it within the column widths.

#### Developer Updates
* Deprecated `GravityView_Edit_Entry::delete_file()` and removed GravityView's handler for the `rg_delete_file` AJAX action, since Edit Entry now deletes removed files when the entry is updated.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.35.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.6.0 Nulled + All Addons
= 3.6.0 on September 24, 2026 =

This update makes removing files in Edit Entry safer, includes security fixes, and resolves issues with Edit Entry, Populate Anything fields, search, and View layouts. We recommend updating.

**Note: GravityView now requires Gravity Forms 2.9.4 or newer.**

#### Improved
* File removal in Edit Entry, which now takes effect only after clicking Update (leaving the page without updating keeps the files).

#### Security
* Improved security when deleting uploaded files in Edit Entry.
* Fixed a data disclosure issue in Edit Entry, limited to users already allowed to edit the entry.

#### Fixed
* The "Hide View data until search is performed" setting did not hide entries from the REST API, CSV and TSV exports, or `[gravityview detail]` counts, and blank searches or searches on fields the View did not offer still showed entries.
* Issues with choice fields populated by Populate Anything:
- Saving an entry in Edit Entry changed or erased choices beyond the first 501, the default maximum Populate Anything loads;
- Inline editing with GravityEdit did not offer saved choices that were not among the loaded choices, so saving erased them;
- Merge tags used outside Custom Content fields showed the stored value instead of the label;
- Custom entry slugs built from these fields switched between the stored value and the label (they now always use the label).
* Issues in Edit Entry:
- Conditional logic restored the wrong value to a dynamically populated field whose parameter name matched an entry property, such as `ip`;
- Calculation fields stopped updating after the first save when the entry had no stored value for them;
- With Gravity Forms 3.1.2, files uploaded to a multi-file field were rejected when the form was resubmitted after a validation error;
- Multi-file upload errors showed "Array" instead of the message for each file.
* Gravity Flow assignees could not delete uploaded files on User Input steps while GravityView was active.
* DataTables column filters had no effect after updating to GravityView 3.5.0.
* View settings added by add-ons, such as GravityMath's Calculation Row Background, went missing from the View editor in GravityView 3.0.
* Search Bar widget issues:
- A large gap appeared between each search field and the Search button in the Horizontal layout on Views not using the Vantage theme;
- Labels for radio, checkbox, date, date range, and number range fields ignored the theme's label styling and appeared at body text size;
- Searches that did not specify a search mode ignored the Search Mode saved on the View and matched any field.
* Layout issues:
- List and Layout Builder Views set to more than one column showed every entry in the first column;
- Entries in Vantage Layout Builder Views lost the space between them;
- Vantage Table Views grew wider than the page when a field held long text instead of wrapping it within the column widths.

#### Developer Updates
* Deprecated `GravityView_Edit_Entry::delete_file()` and removed GravityView's handler for the `rg_delete_file` AJAX action, since Edit Entry now deletes removed files when the entry is updated.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.35.0.

= 3.5.0 on September 24, 2026 =

This release adds default values for Search Bar fields, improves screen reader navigation, and fixes several search, sorting, and display issues.

**Note: GravityView now requires WordPress 6.5 or newer.**

#### Added
* Default Value setting for Search Bar fields, which pre-fills the field and filters the View until a visitor searches, offering a picker of choices for fields that have them.
* "No value" option setting for radio button search fields, adding a choice that clears the field since radio buttons cannot otherwise be deselected.

#### Improved
* Screen reader navigation:
- The Search Bar is a search landmark, the entries are a named region, and the View title names both;
- Pagination arrows and First/Last links have accessible names;
- Radio, checkbox, date, date range, and number range Search Bar fields announce their field name, which screen readers previously skipped;
- Links search fields read as a named list of choices, announcing the field name and the active option.
* Readable query keys in search, sort, and pagination links (for example, `sort[3]` rather than `sort%5B3%5D`).
* Vantage theme styling of DataTables Views: pagination buttons match the rest of GravityView, the page-length control sits at the end of the toolbar, and focus outlines are fully visible.
* Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
* Wider Custom Value box in narrow settings panels.

#### Fixed
* The User Activation field showed "Invalid activation key" instead of the Activate User button on multisite subsites.
* Issues in Views that combine entries from multiple forms ([Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension):
- A Search Bar field from a joined form searched the View's main form instead, matching the wrong entries or none at all;
- Filters on a joined form's fields did not work with relative dates such as "yesterday";
- Sorting by a field did nothing on sites running Gravity Forms older than 3.0.0.1.
* Vantage theme issues in the Search Bar:
- A single-checkbox search field showed its checkbox below the field name instead of beside it;
- Fields in the Advanced Search section ignored the Search Bar's grid, losing their column widths, spacing, and single-column layout on mobile.
* Choosing an option in a Links search field cleared the other search fields' values.
* Views added to a block theme's template or template part through the Site Editor were not recognized as part of the page.
* The `:diff` merge tag modifier (for example, `{date_created:diff}`) was off by the site's UTC offset, so an entry created two hours ago could show as "2 hours from now".
* A `form:` merge tag showed a value from the main form when the target form no longer had that field.
* Filters on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
* The page scrolled when a date picker calendar was opened or closed.

#### Developer Updates
* Added the `GET /wp-json/gravityview/v1/views/{view_id}/refresh` endpoint, used by GravityKit layouts and extensions to fetch a View's entries, entry total, and page window for a given query, and enabled per layout with the `gk/gravityview/view/refresh/live` filter (documented in `docs/view-refresh.md`).
* Added sorting by a joined form's field on any layout with a `sort[<field_id>:<form_id>]` URL parameter, ignoring keys that name a form the View does not join.
* Search Bar fields from a joined form now render the matching `filter_<field_id>:<form_id>` key.
* The `gk/gravityview/view/entries/query/sorting-parameters` filter now provides a `form_id` key on each sorting parameter, identifying the form the sort column belongs to.
* Added the `gk/gravityview/view/output` filter to modify a View's fully rendered HTML before it is returned.
* Added the `gk/gravityview/search/field/default-value` filter to provide or override a Search Bar field's default value.
* The `{gv_entry_link}` merge tag wrote a deprecation notice to the debug log every time it rendered.
* Search Bar fields that hold a group of inputs (radio, checkbox, chained select, date, date range, number range, and entry date) now render as `<fieldset class="gv-search-box ...">` with a `<legend>` instead of a `<div>` with a `<label>`:
- Class names, IDs, input names, and the per-choice `.gv-check-radio` labels are unchanged;
- Custom CSS works with both versions when it leaves the element name off the class (`.gv-search-box`, not `div.gv-search-box`) and targets both field-name elements (`.gv-search-box > label, .gv-search-box > legend`).

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.33.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.5.0 + All Addons
= 3.5.0 on September 24, 2026 =

This release adds default values for Search Bar fields, improves screen reader navigation, and fixes several search, sorting, and display issues.

**Note: GravityView now requires WordPress 6.5 or newer.**

#### Added
* Default Value setting for Search Bar fields, which pre-fills the field and filters the View until a visitor searches, offering a picker of choices for fields that have them.
* "No value" option setting for radio button search fields, adding a choice that clears the field since radio buttons cannot otherwise be deselected.

#### Improved
* Screen reader navigation:
- The Search Bar is a search landmark, the entries are a named region, and the View title names both;
- Pagination arrows and First/Last links have accessible names;
- Radio, checkbox, date, date range, and number range Search Bar fields announce their field name, which screen readers previously skipped;
- Links search fields read as a named list of choices, announcing the field name and the active option.
* Readable query keys in search, sort, and pagination links (for example, `sort[3]` rather than `sort%5B3%5D`).
* Vantage theme styling of DataTables Views: pagination buttons match the rest of GravityView, the page-length control sits at the end of the toolbar, and focus outlines are fully visible.
* Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
* Wider Custom Value box in narrow settings panels.

#### Fixed
* The User Activation field showed "Invalid activation key" instead of the Activate User button on multisite subsites.
* Issues in Views that combine entries from multiple forms ([Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension):
- A Search Bar field from a joined form searched the View's main form instead, matching the wrong entries or none at all;
- Filters on a joined form's fields did not work with relative dates such as "yesterday";
- Sorting by a field did nothing on sites running Gravity Forms older than 3.0.0.1.
* Vantage theme issues in the Search Bar:
- A single-checkbox search field showed its checkbox below the field name instead of beside it;
- Fields in the Advanced Search section ignored the Search Bar's grid, losing their column widths, spacing, and single-column layout on mobile.
* Choosing an option in a Links search field cleared the other search fields' values.
* Views added to a block theme's template or template part through the Site Editor were not recognized as part of the page.
* The `:diff` merge tag modifier (for example, `{date_created:diff}`) was off by the site's UTC offset, so an entry created two hours ago could show as "2 hours from now".
* A `form:` merge tag showed a value from the main form when the target form no longer had that field.
* Filters on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
* The page scrolled when a date picker calendar was opened or closed.

#### Developer Updates
* Added the `GET /wp-json/gravityview/v1/views/{view_id}/refresh` endpoint, used by GravityKit layouts and extensions to fetch a View's entries, entry total, and page window for a given query, and enabled per layout with the `gk/gravityview/view/refresh/live` filter (documented in `docs/view-refresh.md`).
* Added sorting by a joined form's field on any layout with a `sort[<field_id>:<form_id>]` URL parameter, ignoring keys that name a form the View does not join.
* Search Bar fields from a joined form now render the matching `filter_<field_id>:<form_id>` key.
* The `gk/gravityview/view/entries/query/sorting-parameters` filter now provides a `form_id` key on each sorting parameter, identifying the form the sort column belongs to.
* Added the `gk/gravityview/view/output` filter to modify a View's fully rendered HTML before it is returned.
* Added the `gk/gravityview/search/field/default-value` filter to provide or override a Search Bar field's default value.
* The `{gv_entry_link}` merge tag wrote a deprecation notice to the debug log every time it rendered.
* Search Bar fields that hold a group of inputs (radio, checkbox, chained select, date, date range, number range, and entry date) now render as `<fieldset class="gv-search-box ...">` with a `<legend>` instead of a `<div>` with a `<label>`:
- Class names, IDs, input names, and the per-choice `.gv-check-radio` labels are unchanged;
- Custom CSS works with both versions when it leaves the element name off the class (`.gv-search-box`, not `div.gv-search-box`) and targets both field-name elements (`.gv-search-box > label, .gv-search-box > legend`).

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.33.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.4.0 Nulled + All Addons
= 3.4.0 on September 17, 2026 =

This release strengthens the "Prevent Direct Access" setting and fixes several Single Entry, Edit Entry, Custom CSS, and merge tag issues.

#### Improved
* Views with "Prevent Direct Access" enabled now return a "not found" page at their own URL and are excluded from the WordPress sitemap, feeds, archives, and previous/next links, while still working wherever they are embedded and remaining accessible to administrators and editors.

#### Fixed
* The Edit Entry, Delete Entry, and Duplicate Entry link fields did not appear on a user's own Single Entry when that entry was not on the View's first page.
* Single Entry pages in Views with joined forms ([Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension) showed "You are not allowed to view this content." when an Entry Slug was set.
* Long column headings in Table Views using the Vantage theme did not wrap, overlapping the next column.
* Custom CSS and Vantage theme styling did not apply in several places:
- Custom CSS on Views using the Vantage theme had no effect on the Single Entry page unless it used `VIEW_SELECTOR`;
- Custom CSS written with `VIEW_SELECTOR` or `VIEW_WRAPPER`, and Custom CSS on Views using the Vantage theme, had no effect on the Edit Entry page;
- The Vantage theme's typography and style settings did not apply to the Edit Entry page.
* The `{now}`, `{yesterday}` and `{tomorrow}` merge tags showed the wrong time on sites not set to UTC, and did not return UTC when the `:no_tz_offset` modifier was used.
* The `gravityview/template/field/label` filter had no effect on field labels on the [Maps](https://www.gravitykit.com/extensions/maps/) layout's Single Entry page.

#### Developer Updates
* New `gk/gravityview/view/output/direct/404` filter to show the previous message page instead of a "not found" response when a View that prevents direct access is visited at its own URL (return `false`).
* The Edit Entry wrapper (`.gv-edit-entry-wrapper`) now also carries the `gv-container gv-container-{View ID}` classes and a `gv-view-{View ID}-edit-{Entry ID}` id.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.5 Nulled + All Addons
= 3.3.5 on September 10, 2026 =

This update restores Address field Country searching and fixes merge tag pickers in the View editor, both broken by changes in recent Gravity Forms releases.

#### Fixed
* A View setting supplied by an add-on could place unfiltered markup in the View editor.
* The View editor showed every merge tag picker open and unstyled on Gravity Forms 3.1.1 and newer.
* Address field Country issues:
- Searching by country returned no entries submitted since Gravity Forms 3.0.3, which stores the country as its two-letter code;
- The Country input added to a View on its own showed the code (for example, "PR") instead of the country name;
- Searching Country matched every country whose name contains what was searched, so "US" also returned entries from Australia and Austria.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.32.1.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.4 Nulled + All Addons
This release fixes an incompatibility with Gravity Flow on Gravity Forms 3.0 and newer, improves accessibility of the Entry Approval chooser, and includes many other fixes.

#### Fixed
* Edit Entry could not be submitted on Gravity Forms 3.0 and newer when Gravity Flow was active: clicking Update or Next did nothing, with no error and no changes saved.
* A search field's Input Type and other field-specific settings disappeared from its settings window after saving the View until the field was removed and re-added. This affected fields added from your form, including the Gravity Flow workflow fields.
* Edit Entry logged an "Unsupported submission flow detected" warning to the browser console every time it was displayed.
* The Entry Approval field could show and change another form's entry in Views with joins using the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension.
* Entry Approval buttons showed HTML code instead of the approve, disapprove and reset icons when another plugin loaded its own copy of the Tippy tooltip library.
- GravityView's bundled Tippy and Popper libraries broke tooltips in other plugins that bundle their own copies.
* Searching by entry creator on a page showing more than one View could search using another View's settings, returning the wrong entries.
* The Approval Status chooser is now fully usable with a keyboard and a screen reader, in the Gravity Forms Entries list and in Views on your site alike:
- Press Enter or Space on an entry's approval button to open the chooser, the arrow keys to move between Approve, Disapprove and Reset Approval, and Enter or Space to choose one. Escape or Tab closes it and returns you to the approval button;
- A screen reader now says which status an entry is set to, and reports the new status once it changes;
- Opening the chooser with the keyboard no longer jumps the page to the bottom, leaving the chooser and its entry off screen;
- The approval button and the three options are now large enough to be a comfortable target on a touch screen.
* The approval status chooser did not work in a DataTables View until the table was redrawn by sorting or paging.

#### Developer Updates
* Added the `gk/gravityview/edit-entry/form-tag` filter, which modifies the opening `<form>` tag of the Edit Entry form.
* Removed the `gravityview_entries_list-popper` and `gravityview-field-approval-popper` script handles. The bundled tooltip library includes Popper, so the separate file was never used.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.32.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.3 Nulled + All Addons
= 3.3.3 on August 27, 2026 =

This release fixes multiple minor View editor problems that could lose your widgets or your most recent changes, and cleans up field settings that showed up where they do not apply.

#### Security
* Hardens how the Support Port identifies you to our support system.

#### Fixed
* Issues in the View editor:
- Updating a View before the Widgets area fully loaded removed the View's configured widgets;
- Checking one of two mutually exclusive field options, such as opening a link in a lightbox or in a new window, left the other option checked, so both were saved;
- Changes made after a save that another plugin interrupted were missing from the next save;
- Field settings added by other plugins under their own grouping did not appear in the field settings dialog.
- The "Open in a lightbox?" and "Open link in a new tab or window?" field settings appeared when configuring Single Entry and Edit Entry fields, where they do nothing.
* URLs entered with a leading space were rejected as invalid.
* Fields with a Custom CSS Class were missing the separator line above them on single entry screens using the Layout Builder layout.

#### Developer Updates
* Added the `gravityview/merge-tags/setup` JavaScript trigger, fired on `document.body` before GravityView sets up Merge Tag autocomplete in the View editor. Handlers get the textarea and the `wp.codeEditor` instance, and can call `preventDefault()` to take over the field with their own merge tag picker.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.31.1.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.2 Nulled + All Addons
= 3.3.2 on August 20, 2026 =

#### Fixed
* Edit Entry ignored changes to fields, and could clear stored values, on forms where a field with its Gravity Forms visibility set to "Hidden" controls conditional logic or dynamically populated choices.
* View settings that store multiple checkbox choices, such as the Form Notifications setting added by PDF for GravityView, were discarded when saving a View.
* GravityView shortcodes inside code blocks were mangled, showing encoded text starting with `b64:` in place of the attribute values.
* Issues with entry approval in the Gravity Forms Entries list:
- Clicking the approval toggle did nothing, and choosing a status from its popover reported that the request was invalid on WordPress 7.1;
- Confirmation messages did not appear after a bulk Approve, Disapprove, or Reset Approval;
- The approval column was added to forms that do not have any entries yet, so the "no entries" message did not line up with the table.
* Single entry links opened the list of entries instead of the entry on sites running Formidable Forms Pro, when a Formidable view used `entry` as its detail parameter.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.30.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.1 Nulled + All Addons
= 3.3.1 on August 13, 2026 =

This release fixes several issues affecting Views that combine entries from multiple forms, View display settings, and Export Link widget visibility.

#### Fixed
* Issues in Views that combine entries from multiple forms ([Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension):
- The Entry Notes field showed another form's notes;
- Choice-based fields from joined forms were missing the setting that chooses between showing the choice value or the choice label.
* The Export Link widget offered a download link to visitors who are not allowed to export on Views with "Prevent Direct Access" enabled or Views that are not published publicly.
* Issues with View display settings:
- The "Hide the View" and "Hide View until search is performed" settings had no effect on Views using a theme or multiple columns;
- Views lost their theme, custom CSS class, and the "Hide the View" setting when the site's theme contained a GravityView template override.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.29.0.

Decryption key:

To view the content, you need to Sign In or Register.

GravityView - Display Gravity Forms Entries on Your Websites v3.3.0 Nulled + All Addons
== Changelog ==

= 3.3.0 on August 6, 2026 =

This release adds display options to the Entry Notes field, improves drag-and-drop in the View editor, resolves an HTML escaping issue in the View editor, and fixes issues with search, multi-form Views, and the View block.

#### Added
* The Entry Notes field can now display the number of notes, a simple Yes/No, or custom text (merge tags supported) instead of the notes themselves — useful for flagging entries that have been commented on, including in exports.

#### Improved
* Dragging a field in the View editor now follows the pointer, so the zone under the mouse receives the field — narrow and empty zones are easier to target.

#### Fixed
* HTML in a form field's label was output without escaping in the View editor.
* The Entry Notes field exported an empty column to CSV.
* Searching by Entry Date returned the wrong entries on sites with a non-UTC timezone — results were shifted by the timezone offset, so entries from the searched date were missing while entries from a neighboring day appeared.
* Table layouts using a theme other than Legacy displayed a solid white background behind the table, so rounded corners looked square on colored or dark pages.
* Issues in Views that combine entries from multiple forms using the [Multiple Forms](https://www.gravitykit.com/extensions/multiple-forms/) extension:
- Pagination and entry totals counted only the primary form's entries on Gravity Forms 3.0, so pages of results could be missing and reported counts were too low;
- Single entry pages could open the wrong entry, or none at all, on sites that use custom entry slugs.
* Dragging fields in the View editor: the Move and Duplicate buttons wrapped onto a second line in narrow columns, and a field could not be picked up when the drag started on those buttons.
* View block issues in the block editor:
- Enabling Preview loaded the site's front-end styles into the editor and changed its appearance — preview styles now load only inside the editor canvas;
- The block's controls (View selector, Preview toggle) appeared unstyled;
- A preview that failed once kept showing the error after a later preview succeeded.
* An "Entry meta already set" error was repeatedly logged when another plugin (e.g., GravityBoard) had already registered the same entry meta key.
* PHP warnings ("Undefined array key 10") appeared above Views on sites with custom code attached to the deprecated `gravityview_after` action at a non-default priority.
* URLs registered by other plugins (such as Uncanny Toolkit Pro's group sign-up pages) redirected to the home page on sites that use a static front page.
* GravityView's notification events (entry approved, updated, deleted, duplicated) were not sent — with no error — on sites where another plugin modified the form through the `gform_pre_render` filter.

#### Developer Updates
* Views that combine entries from multiple forms now pass an extra `union` key in the SQL fragments array filtered by `gform_gf_query_sql`, holding the `UNION ALL` statements and the subquery's closing alias. Code that rebuilds that array from a fixed list of keys needs to carry it through, or the query loses its unioned forms.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.28.0.