Repository navigation
Bring stored entries across from Gravity Forms and WPForms too - #13
Merged
Merged
Conversation
Importing a form is the half of a migration somebody does immediately; the years of submissions sitting in Flamingo are the half they think of a week later. Forms now remember where they came from and how their fields map, entries import in chunks with their original dates, spam arrives as spam, and running it twice imports nothing twice. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0119U4sRRWGcTQdwYreTwpAp
The registry contract landed with only Contact Form 7 behind it; now all three built-in importers implement the pair. Gravity's entries are read straight from its gf_entry tables, input-id meta assembled into the shape each converted field stores — name parts, address lines, ticked boxes, a List's rows onto the repeater it became. WPForms Pro's entries come out of its fields JSON the same way, and a Lite site, which stores nothing, is accurately offered nothing. Half-typed partial and abandoned entries stay behind: nobody ever sent them. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0119U4sRRWGcTQdwYreTwpAp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
#12 landed the generic entry-migration contract with only Contact Form 7 behind it. This completes the story: all three built-in importers now migrate stored submissions, not just forms.
Gravity Forms
gf_entry/gf_entry_meta— noGFAPI, so it works with the plugin deactivated.5,5.3,5.6) assembled into the shape each converted field stores: name parts and address lines onto composites, one ticked box per dotted row onto checkbox arrays, JSON/comma multiselects, and a List's serialized rows onto the repeater it became.atf_gf_map()recomputes the field map with the same mint-then-drop passes the converter runs (pinned by a test that ids keep counting past a dropped captcha).active+spamcome across;trashstays where somebody put it.WPForms
wpforms_entriestable WPForms Pro writes; a Lite site (which stores nothing) is accurately offered nothing.first/last,address1/postal/…), choice groups split from their newline-joinedvalue.partialandabandonedstay behind — nobody ever sent them; payment statuses likecompletedcome across as ordinary entries.Both reuse the whole generic layer from #12 unchanged: chunked passes, original dates, spam-as-spam, idempotent re-runs, sources never modified.
Tests
docs/hooks-reference.md+readme.txtupdated in the same change🤖 Generated with Claude Code
https://claude.ai/code/session_0119U4sRRWGcTQdwYreTwpAp