Entry Expiration for Gravity Forms | ForGravity | entry

Entry Expiration for Gravity Forms | ForGravity | entry,expiration,gravity forms

Description

Entry Automation for Gravity Forms makes entry deletion more powerful and allows you to export your entries too!

Entry Expiration started out as a simple tool to automatically remove your old form entries. But what if you need more control over when entries are deleted? Want to apply conditional logic to target specific entries? Or maybe delete specific field values rather than the whole entry? Need to generate an export file before getting rid of those entries?

Check out Entry Automation today!

When integrating Gravity Forms with a third-party service, it’s often not necessary to keep entries around after a short period of time as you already have the data imported elsewhere.

Entry Expiration for Gravity Forms allows you to automatically delete Gravity Forms entries older than a defined timeframe. After activating the plugin, set the oldest age for an entry on the Entry Expiration Settings page. At midnight, the plugin will delete all entries on enabled forms that are older than the time you set.

Installation

Requirements

  • WordPress version 3.9.2 and later (tested at 5.5.0)
  • Gravity Forms 1.8.17 and later

Installation

  1. Unpack the download package.
  2. Upload all files to the /wp-content/plugins/ directory, with folder
  3. Activate the plugin through the ‘Plugins’ menu in WordPress
  4. Navigate to the Form Settings page for each form you want to have entries automatically expire and click the ‘Entry Expiration’ tab.
  5. Define how often you want entries to be deleted and the minimum age required for entries to be deleted.

Plugin author

ForGravity

Plugin official website address

https://wordpress.org/plugins/gravity-forms-entry-expiration/
If you encounter problems in using the Entry Expiration for Gravity Forms plugin, you can comment below, and I will try my best to help you solve the problem

Leave a Comment

Your email address will not be published. Required fields are marked *