Repository navigation
Flag Gravity Forms setups that lose submissions - #1
Merged
Merged
Conversation
A form with its honeypot set to "Do not create an entry" loses every real person the honeypot catches (a stale page failing state validation) without a trace. The retention check now lists those forms, one review flag per site, so they can be set to keep caught submissions as spam. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Unless its "save Gravity Forms spam" setting is on, CleanTalk deletes the entry, so a real person it catches is lost. One review flag per blog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gravity Forms rejects every submission from a page cached longer than its state token lives (48 h by default). Where Gravity Forms is active, the collector reads gform_state_lifespan as mu-plugins set it and the check flags anything under 366 days. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The retention check now flags three ways real submissions are lost, each a review flag:
honeypotAction: abort), one flag per site. Unset counts as spam, Gravity Forms' default since 2.9.8GFFormsModel::delete_lead)gform_state_lifespanunder 366 days as mu-plugins set it (default 48 h): every submission from a page cached longer is rejected. Themes and plugins aren't loaded by the collector, so a theme's filter doesn't count; the fix goes in a mu-pluginTests pass (
TestRetentioncovers all three). Checked read-only on one multisite: 43 forms keep honeypot catches as spam, 16 have no honeypot, none throw them away; the lifespan reads 604800 with plugins and themes skipped, so it is flagged until https://github.com/generoi/mutti/pull/229 is deployed. One CleanTalk site has saving on.🤖 Generated with Claude Code