2.13.3 on November 5, 2026
This release improves security for inline editing, so we recommend updating, and fixes issues with approval status, User Registration profile updates, and Entry Tags fields.
🔒 Security
- Improved security when users who can edit only their own entries use inline editing.
🐛 Fixed
- Ticking or unticking GravityView's Approve/Reject field with inline editing saved the field but left the entry's approval status unchanged. The status now follows the field when the person editing can approve entries.
- Inline edits to fields that the Gravity Forms User Registration Add-On copies to a user's profile did not update the profile. They now do when the person editing can edit that user, and send the add-on's "User is updated" notifications. When someone else changes a user's email address, WordPress also emails that user.
- In Views with inline editing, Dynamic Lookup fields that save the chosen text could show the wrong values on every row after the first.
- With GravitySearch active, inline editing stopped working on the Gravity Forms Entries screen after changing pages, sorting, switching status tabs, or searching, and clicking a column name sorted the list instead of opening the column for editing.
- With Gravity Forms 3.0.3 or newer, the Toggle Inline Edit button could not be clicked on an Entries screen showing no entries.
- When editing a whole column at once, clicking a choice's label (Checkboxes, Multiple Choice, Image Choice, and other fields with labels) changed the value in another entry's row.
- Saving the "Other" choice of a Radio Buttons field cleared the field instead of saving the text typed for it.
- Issues with Entry Tags fields:
- On sites with a classic theme, GravityView's Edit Entry showed an empty Entry Tags field for entries whose tags had no colors saved, and saving the entry erased those tags;
- In DataTables Views set to Ajax (Server-side) processing, the inline editor opened empty instead of showing the entry's tags;
- The inline editor's list of tags opened behind the editor, so a tag could only be added by typing it. The list now also closes after you pick a tag, so it doesn't cover the Update button;
- GravityEdit loaded Entry Tags' scripts and styles on every frontend page instead of only where inline editing is on, and on other pages with an Entry Tags field, the list of tags opened on top of the field for logged-in users.
💻 Developer Updates
- Added the
gk/gravityedit/user-registration/can-edit-userfilter to let roles that cannot edit users in WordPress, such as Editors, update a user's account with inline editing. - The role in a User Registration feed now applies only when the person saving the entry can change roles, even with the
gk/gravityedit/user_registration/preserve_rolefilter set to false. - GravityEdit now loads the Entry Tags scripts and styles under Entry Tags' own handles (
gk-entry-tags-public,gk-entry-tags-tagify, andgk-entry-tags-random-color) instead ofgktag_public,tagify, andrandom_color, and no longer loadsgktag_preview. Code that dequeues the old handles has no effect and should use the new ones. - The
gravityview-inline-edit/edit-stylefilter now accepts onlybootstrap3-editable, because thejquery-editableandjqueryui-editablestyles stopped inline editing from starting. Sites that ask for them get the default style, and the GravityEdit log notes it. - The
gravityview-inline-edit/jquery-ui-themeandgravityview-inline-edit/poshytip-themefilters have no effect, since they applied only to thejquery-editableandjqueryui-editablestyles.
🔧 Updated
- Foundation to version 1.39.1.