Columns mapped to a Dynamic Lookup field set to "Multiple Choice" with multiple selections allowed imported nothing even though the import reported success; cells listing the field's stored values, such as record IDs (3, 1), now select those choices.
Entries imported in the background could have no "Created By" user, and imported notes without their own author had none either (both now belong to the user who started the import).
Imports stayed on "Preparing to import…" and never ran when GravityKit's "Enable Background Processing" setting was off but GravityImport's was on (these imports now run in the browser).
With Gravity Forms 3.0.3 or newer, rows rejected for the form as a whole, such as a row whose only value was in a field hidden by conditional logic, were blamed on an anti-spam or CAPTCHA plugin instead of showing Gravity Forms' reason.
Added gk/gravityimport/column/checkbox/delimiter filter to change the separator between choices in a cell mapped to "(Any Choice)" (comma by default).
Melhoria
GravityImport now requires Gravity Forms 2.9.4 or newer.
Imported Quiz entries could have the wrong score, percentage, and grade because the form's last question was skipped and the one before it was counted twice.
File Upload field issues: Files imported into a single-file File Upload field created with Gravity Forms 2.10 or newer did not appear on the entry, its Edit screen, in Views, or in merge tags, even though the files were downloaded;; When a row kept a file link formatted as a list (such as [" "]), files downloaded into other File Upload fields in that row were lost;; After a row failed to import, later rows stored single-file File Upload values as a list instead of a single link.
A CSV column mapped to the "(Any Choice)" option of a Checkboxes, Multiple Choice, or Image Choice field left every box unchecked when a cell listed several comma-separated choices (for example, friday,saturday).
The "Email Will Be Rejected" notice on the Map Fields step showed "%s" instead of the email patterns Gravity Forms rejects.
The format dialog for unrecognized dates and times named MM/DD/YYYY or hh:mm AM/PM as the default even when another format was in use, such as YYYY-MM-DD hh:mm:ss for Entry Date.
Foundation to version 1.35.0.
Versão 2.12.2
3 melhorias
Melhoria
GravityImport now requires WordPress 6.5 or newer.
Issues when importing Consent fields: The form's consent text could be overwritten, and imported entries linked to the wrong version of the terms;; Consent terms containing % or _ were saved as a new version on every import.
Files were not imported into file upload fields on Gravity Forms 3.1.2 or newer, which rejected every row with "The file is not valid."
Multiple Choice and Image Choice fields set to "Select One" could not be mapped as a single column, the mapping step offered only their individual choices, and the column was dropped while the import still reported success.: Existing mappings to an individual choice are now rejected with a message naming the field to map instead, or skipped with a warning when an import profile runs from the command line.
Multiple Choice and Image Choice fields that allow more than one selection stored cell values such as 1, yes, 0 or no as the selected choice instead of treating them as Checkbox columns do.: 1, true or yes selects the choice, while 0, false, no or an empty cell leaves it unselected;; "(Any Choice)" is available as a mapping target;; Rows that don't meet an "Exact Number" or "Range" selection limit are reported as errors.
Row errors showed HTML character codes such as < and & in the import log and the failed records download, including around formatted text in Gravity Forms messages.
Rows rejected by a form-level validation failure now report the actual cause instead of "Failed validation: Unknown", including when Gravity Forms is blocking submissions while its database upgrade is pending (common on freshly cloned staging sites), or when an anti-spam or CAPTCHA plugin rejects the submission.
Entries imported with an Entry Status column using different capitalization (e.g., Active) could not be opened or edited in GravityView; the standard statuses (active, spam, trash) are now saved in the lowercase form Gravity Forms expects.
Imports with a file upload column failed on Gravity Forms 3.0+, downloaded files are now given a temporary name matching the uploaded file's extension, which Gravity Forms 3.0+ requires.
A row rejected by a multi-file upload field caused a fatal error on PHP 8; on PHP 7.4 the error named the field but left the reason blank.
Foundation to version 1.27.0.
Correção
Resolved a "translation loading was triggered too early" notice on WordPress 6.7+.
Imports to forms mapped to a Pod via the Pods Gravity Forms add-on now import reliably: every row is saved to the Pod, and a row that leaves a required Pods field empty no longer stops the whole import.
A feed that errors while importing a row no longer stops the whole import; the row is recorded as an error and the import continues.
Added gk/gravityimport/source/allowed-wrappers filter to control which PHP stream-wrapper schemes are accepted as import sources.
Melhoria
Imports failed on hosts where uploaded files are not served from the local filesystem (for example, vip:// on WP VIP or s3:// on sites using object storage).
Added gk/gravityimport/processor/background/enabled filter to programmatically control whether background processing runs for an import, either site-wide or per form. The filter receives the resolved boolean and an optional form ID.
Melhoria
Ability to save field mappings and import options as a downloadable file that can be loaded to restore the same configuration on subsequent imports.
Support for importing files from the command line via WP-CLI.
"Enable Background Processing" setting under GravityKit → Settings → GravityImport to turn off background imports site-wide and force synchronous processing.
On the import completion screen, the "Modify Import Configuration" and "Change Field Mapping" buttons are now labeled "Retry N Failed Records" and "Remap & Retry N Failed Records" to make it clearer that the retry action applies only to failed rows.
Faster loading of the form picker on the importer page.
Background import processing: Imports now run in the background, you can close the browser tab and return later;; A live progress notice appears across the WordPress admin with a link back to the import page;; Pause, resume, and cancel controls are available on the import page.
Failed record recovery: Retry only the rows that failed, using the same field mapping or an updated one;; Download failed rows as a CSV, including a column explaining why each row failed.
Better memory handling when processing imports with many failed records.
Conditional logic settings from a previous import no longer carry over when the option is disabled on the Configure step.
Cancelled imports now correctly report skipped and errored rows in the summary.
"Ignore Field Conditional Logic" toggle not appearing in the Configure step, causing imported field values to be cleared when conditional logic conditions were not met by the CSV data.
Redesigned field mapping interface with a vertical layout that's easier to scan and work with, especially for CSVs with many columns.
Pre-import validation warnings that highlight potential data issues like invalid emails, non-numeric values, or unrecognized date/time formats before importing.
Checkboxes to quickly select or deselect which columns to import, with a header checkbox to select or deselect all.
Auto-map button to reset field mappings to auto-detected values, with a confirmation dialog to prevent accidental resets.
Cell-level validation highlighting in the data preview, making it easier to spot exactly which values need attention.
Inline column name editing for renaming CSV column headers before importing.
Validation now checks up to 50 rows of data (previously 10), giving a more accurate picture of potential issues before importing.
Date and time formats are now auto-detected from CSV data instead of requiring manual selection.
Datetime values with milliseconds (e.g., 2024-12-01 00:43:21.000) are now parsed correctly.
Smarter field matching means fewer manual adjustments when mapping CSV columns to form fields.
Entry Notes now requires exact column name matches, preventing accidental mapping of unrelated columns.
Better keyboard navigation: use Tab to move between fields, Enter to confirm selections, and Escape to cancel edits.
Improved screen reader support and accessibility throughout the import interface.
Better support for right-to-left (RTL) languages.
The "Ignore Field Conditional Logic" option now only appears when the form actually has conditional logic.
Fatal error when importing List field data on PHP 8+.
Foundation to version 1.3.1: New GravityKit global settings for logging configuration (level, type, cleanup schedule, retention);; A unified way to display admin notices across all GravityKit products;; Performance improvements and bug fixes.
Melhoria
Importing GravityView's Approval Status values now works with both text labels ("Approved", "Disapproved", "Unapproved") and their numeric equivalents (1, 2, 3).
PHP 8.1+ warnings and intl extension conflict on some hosts.
Versão 2.6.0
5 melhorias
Melhoria
Import performance and reliability have been enhanced with smarter memory and timeout management.
The import process now better detects available server resources and adjusts accordingly.
Large CSV imports are now more stable and less likely to fail due to resource constraints.
Foundation to version 1.2.25.
Refactored server resource management into a dedicated Server helper class.
2024
3 versões
Versão 2.5.1
2 melhorias
Melhoria
PHP notice in WordPress 6.7 caused by initializing product translations too early.
Foundation to version 1.2.21.
Versão 2.5.0
1 novidade1 melhoria
Novidade
Added gk/gravityimport/rest/request-validation-skip-params filter to allow customization of which REST request parameters are excluded from validation when processing batch requests.
Melhoria
Foundation was updated to version 1.2.17.
Versão 2.4.10
1 novidade2 melhorias
Novidade
Added a gk/gravityimport/ui/form-data filter to modify the form data object for use in the UI.
Melhoria
A deprecation notice in PHP 8.1+ caused by passing null as a parameter to built-in string functions.
Foundation was updated to version 1.2.7.: Improved the setting and retrieval of transients when using object cache plugins.; Fixed a JavaScript warning that appeared during the deactivation of license keys.
2023
5 versões
Versão 2.4.9
2 melhorias1 correção
Melhoria
Support for RTL languages
Foundation to version 1.2.2
Correção
Auto-mapping of the User IP field not working
Versão 2.4.8
1 melhoria
Melhoria
Foundation to version 1.1.1
Versão 2.4.7
1 melhoria1 correção
Melhoria
Foundation to version 1.0.12
Correção
Incompatibility with some plugins/themes that use Laravel components
Versão 2.4.6
1 novidade2 melhorias
Novidade
Option to ignore field conditional logic during import
Melhoria
GravityImport now requires PHP 7.2 or newer
Foundation to version 1.0.10
Versão 2.4.5
1 melhoria
Melhoria
Foundation to version 1.0.8
2022
12 versões
Versão 2.4.4
2 correções
Correção
PHP 8.1 notices
Fatal error on some hosts due to a conflict with one of the plugin dependencies (psr/log)
Versão 2.4.3
1 correção
Correção
It was not possible to remove an expired license key
Versão 2.4.2
1 correção
Correção
"Undefined index" PHP notice
Versão 2.4.1
3 correções
Correção
Fatal error when loading plugin translations
Slow loading times on some hosts
Plugin failing to install on some hosts
Versão 2.4.0.3
1 correção
Correção
Plugin was not appearing in the "Add-Ons" section of the Gravity Forms System Status page
Versão 2.4.0.2
1 correção
Correção
Potential error when the plugin tries to log an unsuccessful operation
Versão 2.4.0.1
1 correção
Correção
Error when trying to activate license keys
Versão 2.4
1 novidade1 melhoria
Novidade
New WordPress admin menu where you can now centrally manage all your GravityKit product licenses and settings (learn more about the new GravityKit menu): Go to the WordPress sidebar and check out the GravityKit menu!; We have automatically migrated your existing GravityImport license, which was previously entered in the Gravity Forms settings page; Request support using the "Grant Support Access" menu item