Todas as versões registradas, da mais nova para a mais antiga, com o que mudou em cada uma.
Última 2.13.115 versões
Sem data · 15 versões
2.13.1
Última
1 melhoria5 alterações
Melhoria
Improved security when inline editing List fields.
Alterações
This release improves security for inline editing List fields and fixes an error when saving inline edits in some filtered Views; we recommend updating.
🔒 Security
Users who can edit only their own entries saw a "You are not allowed to edit this entry" error when inline editing in Views whose Advanced Filtering uses a value from the page, such as `{get:...}`, `{current_post}`, `{embed_post}`, or `{custom_field}`.
🔧 Updated
[Foundation]
2.13.0
1 melhoria17 alterações
Melhoria
Improved security when displaying Entry Tags values after inline editing.
Alterações
This release adds inline editing of Entry Tags fields in GravityView Views, improves security (we recommend updating), and fixes several issues with inline editing Entry Tags and Dynamic Lookup fields.
Inline editing of Entry Tags fields in GravityView Views (requires Entry Tags 1.5.0 or newer).
🔒 Security
Inline editing could allow unintended changes to entries under certain conditions.
Issues with inline editing Entry Tags fields
Saving on the Gravity Forms entries list never finished
The inline editor showed the tags of the first entry on the page alongside the entry's own tags, and saving kept them
A tag containing a quotation mark or `
Tags saved as comma-separated text (for example, by an import) opened as plain text instead of in the tag picker
An entry with damaged Entry Tags data stopped inline editing from working for every field below it.
Issues with inline editing Dynamic Lookup fields
Fields whose selected record was no longer one of their choices (for example, an entry moved to the trash) showed no selection and were cleared on save
Checkboxes could show the wrong boxes ticked after their choices changed, and inline editing another field could remove those selections.
Saving a field inline removed backslashes from its value (except in Paragraph Text fields).
Opening another field while an inline editor was open took two clicks when Inline Edit Mode was set to "In-Place" or when editing a whole column.
🔧 Updated
[Foundation]
2.12.0
14 alterações
Alterações
This update restores inline editing after a View refreshes its entries and fixes issues that could erase or misplace selections in choice fields.
Note: GravityEdit now requires WordPress 6.5 or newer.
Inline editing stopped working after a View refreshed its entries without reloading the page, leaving the Toggle Inline Edit link and editable fields unresponsive.
Issues that could erase saved values in choice fields, especially those filled in by Populate Anything
Multi Select fields listed the first entry's choices when editing any entry, so saving could erase values when entries had different choices
Radio Buttons and Checkboxes fields could lose their value on save when entries had different choices or the saved choice was beyond the first 501 that Populate Anything loads
Inline editing any field could clear selections in a Checkboxes field filled in by Populate Anything when its choices depended on another field or a selection was beyond the first 501.
Selections in Image Choice and Multiple Choice fields could appear unchecked in Gravity Forms after saving if the field's choices had been reordered or deleted.
Display issues after saving a field
Multi Select fields showed stored values instead of choice labels
Image Choice field labels ran together
Image Choice fields using the "Input value" display option showed images instead of values.
🔧 Updated
[Foundation]
2.11.2
6 alterações
Alterações
This release fixes adding links with the rich text editor.
Issues adding a link with the rich text editor
With Inline Edit Mode set to Popup (the default), the link box, its suggestions list, the Link options dialog, the toolbar tooltips and the Keyboard Shortcuts window opened behind the popup and could not be used
Searching for content to link to returned no results in a View.
🔧 Updated
[Foundation]
2.11.1
10 alterações
Alterações
This release resolves several Inline Edit issues in embedded Views, along with column editing and a missing toggle button under WordPress 7.1 and Gravity Forms 3.0.3 or newer.
Note: GravityEdit now requires PHP 7.4 or newer.
Clicking the first column's header in the entries list did not open that column's fields for editing on WordPress 7.1.
The Inline Edit toggle button disappeared on an entries list with no entries when using Gravity Forms 3.0.3 or newer.
Issues when one View is embedded inside another, using either a Custom Content field or the GravityView View field
The "Enable Inline Edit" button toggled every editable View nested in or around it instead of only its own, leaving labels out of sync with whether fields were actually editable
An embedded View did not keep its own Inline Edit setting between page loads, because the setting was saved under the surrounding View's name
An embedded View was dimmed, and its links and its own toggle button stopped working, whenever the surrounding View had Inline Edit turned on.
🔧 Updated
[Foundation]
2.11.0
1 melhoria27 alterações
Melhoria
Improved data validation and security when saving edited fields.
Alterações
This release adds a rich text editor for inline editing, restores Gravity Forms 3.0 compatibility for phone and masked text fields, and strengthens data handling and security.
A rich text editor for inline editing. Paragraph fields that use the rich text editor are now edited in place with a formatting toolbar (bold, italic, underline, lists, quotes, and links) instead of showing HTML tags, and your formatting is saved exactly as you see it. Submit with the Update button or Cmd/Ctrl+Enter, and cancel with Esc.
✨ Improved
An entry can no longer be edited through a form it does not belong to.
Strengthened permission checks for the inline file-upload action.
Inline uploads now honor the field's allowed file types, rejecting a disallowed type with a clear message.
Better compatibility with PHP 8.0, 8.4, and newer versions.
Files larger than the field's maximum size are now rejected, with a clear message.
More detailed error logging when number field calculations fail to update.
Deleted or unavailable Views no longer cause fatal errors.
List field values were not showing correctly when editing, resulting in empty or incorrect data.
Uploaded files could be saved to the wrong directory when multiple uploads happened on the same page.
Button and toggle text with special characters (like quotes or ampersands) could display incorrectly.
Number fields with calculations stopped updating when a single calculation failed.
The User Registration Add-On integration was triggering errors before verifying the Add-On was active.
PHP notices when editing checkbox, select, survey, and radio fields with missing choice values.
Product field errors when the field data was unavailable.
Entry Creator, Source URL, Date Created and Entry Tags could not be edited inline.
An inline edit that failed to save could still appear to have saved, showing a value that was not stored.
Clearing a file upload field that held multiple files removed only the first file, leaving the others on the server.
Phone fields set to Gravity Forms 3.0's "International (formatted)" format could not be edited inline: every edit was rejected and the entry kept its old number. This is the format Gravity Forms 3.0 gives a new phone field, and the one it falls back to for a phone field with no format of its own.
Text fields with an input mask rejected every inline edit on Gravity Forms 3.0, which began checking the mask when the entry is saved. The mask's punctuation is now filled in for you, so typing `5559876543` into a `(999) 999-9999` field stores `(555) 987-6543`. A value the mask cannot hold is still refused, with Gravity Forms naming the format it expects.
The "Toggle Inline Edit" button never appeared on an entries view with no rows, such as a search that matched nothing or an empty Trash filter.
💻 Developer Updates
Inline edit saves now use `GF_Field::get_value_save_input` on Gravity Forms 3.0+ instead of the deprecated `GFFormsModel::prepare_value`.
Inline edit saves for number, product, and address fields now use `GF_Field::get_value_entry_detail` instead of `GFCommon::get_lead_field_display`, deprecated in Gravity Forms 3.0.
Now uses the current GravityView hooks instead of ones deprecated in GravityView 2.55.
2.10.0
1 melhoria3 alterações
Melhoria
Compatibility with Gravity Forms 2.9.29+ where inline editing of number, product, and address fields triggered PHP warnings.
Alterações
This release includes internal component updates and bug fixes for improved stability and compatibility, and fixes a PHP warning.
🔧 Updated
[Foundation]
2.9.2
6 alterações
Alterações
This release fixes inline editing of dynamically populated choice fields, such as those using GP Populate Anything.
Multiple issues with inline editing of dynamically populated choice fields (e.g., via GP Populate Anything)
Checkbox values were wiped or corrupted when saving
Editing an unrelated field in the same entry corrupted checkbox values
Choice labels were replaced with raw IDs/values after saving
Select fields displayed raw values instead of labels.
2.9.1
5 alterações
Alterações
This release fixes inline editing issues affecting Email and Dynamic Lookup fields.
Inline editing always showing a "Your emails do not match" error for Email fields with confirmation enabled.
Dynamic Lookup field values not visually updating after inline editing until the page was refreshed.
🔧 Updated
[Foundation]
2.9.0
1 novo8 alterações
Novo
Added `gk.datatables.inline-edit.refresh` JavaScript filter to override whether the DataTables table refreshes after an inline edit save.
Alterações
This update lets you control whether DataTables refreshes after saving inline edits, and resolves issues with Single Entry lightbox, Custom Content field links, and session handling.
View editor setting to control whether the DataTables table automatically refreshes after saving an inline edit.
JavaScript error ("View ID is undefined when setting initial state") when viewing a single entry in a GravityView lightbox.
Links in Custom Content fields were not clickable when inline edit mode was active.
Inline edits failing silently when the user's session expired, causing changes to appear saved but revert on page reload.
💻 Developer Updates
🔧 Updated
[Foundation]
2.8.0
5 alterações
Alterações
This release improves the inline editing experience for DataTables users.
✨ Improved
Views using the [DataTables]
🔧 Updated
[Foundation]
2.7.1
5 alterações
Alterações
This update fixes incorrect display of the Image Choices field and Entry Tags field editing on the Entries page.
Image Choices field incorrectly displaying images for choices with empty values.
[Gravity Forms Entry Tags]
🔧 Updated
[Foundation]
2.7.0
4 alterações
Alterações
This release adds the ability to edit survey responses.
Support for editing Gravity Forms Survey Add-On fields (Likert, Rating, Rank, etc.)
🔧 Updated
[Foundation]
2.6.0
5 alterações
Alterações
This update adds support for the Multiple Choice field and fixes unintended HTML markup in exported entries.
Support for editing Multiple Choice field values (Gravity Forms 2.9+).
Field values were wrapped in GravityEdit-specific HTML markup when exporting View entries using the Export widget.
🔧 Updated
[Foundation]
2.5.1
1 novo1 melhoria1 removido7 alterações
Novo
New GravityKit global settings for logging configuration (level, type, cleanup schedule, retention)
Melhoria
Performance improvements and bug fixes.
Removido
Removed early `is_user_logged_in` return to allow for the `gravityview/capabilities/allow_logged_out` and `gravityview/edit_entry/user_can_edit_entry` filters to be applied when checking whether inline editing is enabled on the frontend.
Alterações
This update fixes broken thumbnails after file uploads and a possible fatal error triggered when a View has an Entry Tags field without the required plugin active.
Cache not clearing after file uploads, which caused broken thumbnails on refresh.
Fatal error when inline editing was active on a View with an Entry Tags field and the [Gravity Forms Entry Tags]
💻 Developer Updates
🔧 Updated
[Foundation]
A unified way to display admin notices across all GravityKit products
Changelog publicado pelo desenvolvedor, no idioma original.
