UAU Ready
Description
The GravityRevisions – Track Changes to Entries add-on records the complete change history in Gravity Forms forms and entries, saving who changed each field, what the change was, and when it occurred. The extension complements GravityKit by enabling one-click restoration to any previous version, side-by-side comparison between revisions, and email notifications when an entry is updated.
Key Features
- Change history
Records every modification in forms and entries, including author, changed field, and date. - One-click restoration
Reverts a form or entry to any previously saved version in the history. - Side-by-side comparison
Displays earlier versions in two columns to identify differences between revisions. - Email notifications
Sends real-time alerts to administrators whenever an entry is edited. - Display via GravityView
Shows the revision history on the site front-end through integration with GravityView.
Benefits of GravityRevisions – Track Changes to Entries
- Reliable auditing
Tracks accountability in every edit, useful for teams with multiple administrators. - Fast error recovery
Lets you undo improper changes without needing to restore a database backup. - Workflow visibility
Makes the lifecycle of collected data in forms transparent. - Compatibility with workflows
Provides actions and filters to integrate version control into custom workflows.
Who Is It For?
- Teams that manage Gravity Forms with multiple editors and need an audit trail.
- High-traffic sites where entries are edited frequently and require safe rollback.
- GravityView users who want to expose the revision history directly on the front-end.
The GravityRevisions – Track Changes to Entries add-on adds version control to the GravityKit ecosystem, turning edits in forms and entries into a navigable, comparable, and reversible history. Recommended for administrators who handle sensitive data, editorial teams, and collaborative sites, it reduces the risk of information loss and keeps a record of who did what at each stage of the submission flow.
Frequently asked questions
Is GravityRevisions – Track Changes to Entries GPL-licensed?
Yes. GravityRevisions – Track Changes to Entries is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use GravityRevisions – Track Changes to Entries on multiple sites?
Yes. You can use GravityRevisions – Track Changes to Entries on multiple sites. The number of sites connected to Ultrapack Auto Updater is limited by your plan.
How much does GravityRevisions – Track Changes to Entries cost at Ultrapack?
GravityRevisions – Track Changes to Entries costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does GravityRevisions – Track Changes to Entries include updates?
Yes. The current version of GravityRevisions – Track Changes to Entries is 1.9.0, published at Ultrapack on Aug 27, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is GravityRevisions – Track Changes to Entries scanned before publication?
Yes. Every version of GravityRevisions – Track Changes to Entries goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin GravityRevisions – Track Changes to Entries?
Requires WordPress 5.1 or higher and PHP 7.2.0 or higher. Tested up to WordPress 7.1.0.
What changed in this version
Version 1.9.0
- This release expands form revisions with a pre-restore backup, versioned notifications and confirmations, a Forms list revision count, and new developer hooks, plus fixes to form restore and revision counting.
- Backs up the current form as a new revision before a restore, so a restore can be undone.
- Includes form notifications and confirmations in form revisions, so they are versioned and restored with the form.
- Adds a revision count to the Gravity Forms Forms table.
- A form revision being applied to the wrong form — revisions are now validated against their own form before restoring.
- A single form save creating more than one revision, inflating the revision count.
- Editing a notification or confirmation on its own not creating a form revision, leaving the change out of the form's revision history.
- A "translation loading was triggered too early" notice on WordPress 6.7 and later, caused by loading settings translations during startup.
- 💻 Developer Updates
- Adds `before`/`after` actions around form-revision save, restore, and delete
- `gk/gravityrevisions/form-revisions/save/before` and `/after`
- `gk/gravityrevisions/form-revisions/restore/before` and `/after`
- `gk/gravityrevisions/form-revisions/delete/before` and `/after`.
- Adds the `gk/gravityrevisions/entry-revisions/restore/after` action, which fires after an entry has been restored from a revision and receives the entry ID, the entry before the restore, the restored entry, and the revision ID — restoring suppresses Gravity Forms' entry update hooks so notifications and feeds don't fire, which also leaves anything caching entry data (a calendar subscription, a search index) with nothing else to listen for.
- 🔄 Updated
- [Foundation]
Version 1.8.0
- This release includes internal component updates and bug fixes for improved stability and compatibility.
- 🔄 Updated
- [Foundation]
Version 1.7.2
- This release fixes a fatal error when activating GravityView alongside GravityRevisions and resolves missing revision notifications with async sending enabled.
- A fatal error could occur when activating GravityView while GravityRevisions was already active.
- Revision notifications were not sent when async notifications were enabled in Gravity Forms 2.9.31.3 or later.
- 🔄 Updated
- [Foundation]
Version 1.7.1
- This update fixes a regression from the 1.7.0 update that disabled entry revisions on existing forms, resolves issues with global revision settings, and addresses a fatal error with Gravity Perks Nested Forms.
- Entry revisions were disabled on all forms that existed prior to the 1.7.0 update.
- Changes to the global entry and form revision settings in GravityKit > Settings > GravityRevisions were not taking effect.
- Fatal error when submitting a form that uses Gravity Perks Nested Forms (GPNF) with GravityRevisions active.
- 🔄 Updated
- [Foundation]
Version 1.7.0
- Form setting to enable or disable entry revisions for each form.
- Global settings under GravityKit > Settings > GravityRevisions to enable or disable form and entry revisions by default for all forms.
- 🔄 Updated
- [Foundation]
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
- Download the file
gravityview-entry-revisions.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
gravityview-entry-revisions.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 5.1 or higher and PHP 7.2.0 or higher. Tested up to WordPress 7.1.0.
Stuck on a step? Open a ticket telling us which one you stopped at.
