GravityView Revisions

Original file

Version

1.9.0 Changelog

Updated

31 Aug 2026

Auto-update

Yes How it works

File scan

Clean Details

Members can request updates and report problems from here.

About this template kit

GravityView Revisions is a handy add-on for GravityView that automatically tracks changes to Gravity Forms entries, giving site owners and developers a clear history of every edit made.

It’s perfect for membership sites, directories, and any project where data accuracy matters. You can compare entry versions side by side and restore previous records with a click, making it easy to catch mistakes or roll back unwanted changes without losing anything.

Changelog

Version 1.9.0

Latest 27 Aug 2026

3 new1 fixed10 changed

New

Adds a revision count to the Gravity Forms Forms table.
Adds before/after actions around form-revision save, restore, and delete:
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 se...

Fixed

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.

Changed

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.
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.
Gk/gravityrevisions/form-revisions/save/before and /after
Gk/gravityrevisions/form-revisions/restore/before and /after
Gk/gravityrevisions/form-revisions/delete/before and /after.
Foundation to version 1.31.0.

Earlier versions