Jordan Pope asked 1 month ago
Title. I can't even seem to make a submission here on this forum.
Peter Walters answered 1 month ago
I have the same issue. Is there a way of rolling back Formidable Lite, without doing a full backup and losing my entries from then to now?
Paul Bruikman
replied 1 month ago From the support thread on WP I got this:
WP Rollback plugin:
https://wordpress.org/plugins/wp-rollback/
Use it to roll back formidableforms to 6.20
Worked for me. I did not downgrade pro.
Jordan Pope
replied 1 month ago This is the answer. Personally though I just rolled back my whole site with a backup as I take auto backups every night. Comes in handy for situations like this! I will wait for a few versions of Formidable to rollout before testing my feet in the water again to make sure the issue is fixed.
Christopher Simmons answered 1 month ago
This new filter solved it for us
add_filter( 'frm_check_denylist', '__return_false' );
Christopher Simmons
replied 1 month ago heh... yeah, went to put in a support ticket 'the sky is falling' and first box on second page was about this issue. So, yeah, big annoyance f or us since we use forms for client projects which are time sensitive in PR business. Two clients in two days unable to submit projects for no discernible reason. This code fixed it instantly. #whew -- should have been more notable warning about this in WP after this week's update where it came to life.
Christopher Simmons
replied 1 month ago Weird. The filter if setup properly is the correct option to disable the spam check. Worked for our site, but obviously might not work for every install; we're using FF Pro.
Jordan Pope
replied 1 month ago Probably misconfigured somehow in my frantic rush to correct the issue lol. Nevertheless, it seems like v6.21.1 is addressing the issue, although personally I'm going to wait a bit to update again as I don't have the bandwidth to troubleshoot this niche issue at the moment
helen dorward answered 1 month ago
Thank you the rollback plugin fixed my issue, not ideal but it has fixed it for now, all submission of one heavily used form marked as spam before this.
Rob LeVine Staff answered 1 month ago
btw, 6.21.1 supposedly fixed this issue.
Formidable Forms v6.21.1 - May 14, 2025
New: A new setting, Check denylist data to validate for spam, has been added to Global spam settings. This new spam check was causing too many false positives, so it is now disabled by default.
New: When a denylist check is enabled, spam keywords that are detected are now stored in a transient and displayed in Global spam settings, under Custom allowed words. This makes it easier to detect and add exceptions when spam is detected.
New: Denylist checks will no longer check radio buttons, checkboxes, dropdowns, signature, password, and CAPTCHA fields to help avoid issues with false positive matches. Fields with options will still validate “Other” input values.
New: All spam checks are now disabled when importing forms.
Fix: The way the honeypot field ID is determined has been updated to avoid conflicts with other forms.
Fix: User defined product fields would fail validation.
Please login or Register to submit your answer
Wow, it finally worked. It was even marking my submissions here as spam. Here is more detail.
I have multiple websites all using Formidable Forms Elite for various things, mostly lead generation with Quote Forms.
Since my sites automatically updated to v6.21 last night, all client form submissions are marked as spam and submission is prevented. It seems very likely this is related to your changes to the spam system from 6.20 > 6.21.
Even with ALL spam settings disabled the issue persisted across all sites. I even tried to disable and reinstall the plugin and disable all of my other plugins and my theme, and it did not fix the issue. I was only able to resolve by reverting to v6.20 across the board.
While I have since rolled back to v6.20, as mentioned, I was not able to find any useful information in Formidable Logs or Reports explaining why this was happening either. I had to rollback all of my sites as well which means I have lost access to any useful information relating to the issue, unfortunately.