WordPress installation
Download formconfirmed for WordPress (ZIP)
- In WordPress, go to Plugins → Add Plugin → Upload Plugin. Upload the ZIP, click “Install Now” and then “Activate Plugin”. Older WordPress versions may call Add Plugin “Add New Plugin” or “Add New”.
- Open Settings → formconfirmed → “Settings” and choose “Connect with formconfirmed”.
- Open your formconfirmed account, compare the website and request code and approve the connection.
- Return to WordPress and complete the connection.
- Open the “Forms” tab, enable the forms you want to protect and save. New forms follow the default setting shown there. If you use a page cache, clear it after saving.
- As a visitor, open one of your protected forms, check for the formconfirmed badge and send a harmless test message. Check that it arrives.
- In the plugin, check that “Overview” shows a recent response. Marked submissions are listed under “Held messages”.
Manual keys (alternative)
Manual keys remain available under “Settings”. Add your website to your formconfirmed account, enter the site key and secret key and test the connection. The secret key belongs only on your server.
Contact Form 7
In the “Forms” tab, enable the required Contact Form 7 form. Existing forms receive the protection automatically. The optional form tag [formconfirmed] is also available for an explicit widget position.
WPForms
In the “Forms” tab, enable the required WPForms form. Submit a normal message on the public page and check delivery through the notification channel configured in WPForms.
Already using the formexposed plugin? You can also set up formconfirmed under its Form protection tab.
Set up more form types
First connect WordPress using the seven steps above. These additional notes explain the selection and behavior of each integration.
Gravity Forms
The formconfirmed Forms tab lets you select each detected Gravity Forms form individually.
- Enable Gravity Forms and the required form in the Forms tab. For new forms, also check the setting that automatically protects newly created forms.
- Open the published form page as a logged-out visitor. Use Field mapping for name, email and message if needed; passwords and uploads cannot be enabled for message analysis.
- After a test submission, check the entry status and any formconfirmed spam-filter note in Gravity Forms. Every submission the plugin does not pass is treated as spam there.
Limits: The normal Gravity Forms confirmation alone proves neither spam classification nor delivery. Test multipage forms, AJAX and Save and Continue in your actual combination; no version compatibility approval is asserted here.
Elementor Pro
This integration targets the Elementor Pro form widget. It does not imply support for Elementor Free or every newer form type.
- Enable Elementor Pro in the formconfirmed Forms tab. It has one shared switch, with no selection per Elementor form.
- Check the published page outside the editor. The plugin inserts the widget during rendering; a missing badge alone does not prove protection is absent.
- Submit normal data on your test installation and check the configured Elementor notification. If formconfirmed does not pass the submission, the adapter shows an error; it does not provide a normal confirmation while holding the Elementor email.
Limits: Popup forms, multistep flows, Theme Builder templates and Element Caching need their own checks. A review copy is not guaranteed because storage has limits and may use another quarantine integration.
Fluent Forms
Detected Fluent Forms forms can be enabled individually in the Forms tab.
Requirements
- Administrator access to WordPress.
- formconfirmed 1.6.1 requires WordPress 6.2 or later and PHP 7.4 or later.
- Fluent Forms is active. formconfirmed detects it by the constant
FLUENTFORMorFLUENTFORM_VERSION; formconfirmed does not require a Pro edition. According to Fluent Forms, multi-step forms (“Form Step”) need the Pro add-on. - Versions: formconfirmed names no Fluent Forms version. It uses hook names with a slash (e.g.
fluentform/validation_errors); according to Fluent Forms these names exist since version 5.0. This is a deduction, not a test: this guide promises compatibility with no Fluent Forms version. Use a current release and check with the test below. - formconfirmed is connected to your account: steps 1 to 4 of the WordPress guide.
Which forms are covered
| Form type | Status |
|---|---|
| Normal Fluent Forms forms | The server places the element before the submit button; each form can be switched individually. |
| Multi-step forms (Pro, “Form Step”) | The code provides for a helper script that adds the element in the browser. Not tested. |
| Conversational forms | Not mentioned in the code, not confirmed. Check on a test page before use (element fcp-widget, result in the form). |
What happens on submission
- If Fluent Forms itself already reported an error (required field, its own spam protection), formconfirmed does not ask the service.
- Clear “allow”: Fluent Forms saves the entry under “Entries” and sends your notifications as usual.
- No clear answer from the service: the submission only goes through normally if the backup check on your server is switched on and passes. For “flag” and “block” it is not used.
- In all other cases the form shows an error message. According to Fluent Forms, a validation error means no entry is saved and no notification is sent. Fluent Forms cannot hold a message back: even with “Hold for review” the visitor sees an error.
- formconfirmed also tries to keep a copy under “Held messages”, named after the form title. That does not always work, see “When no copy is kept”.
Messages visitors may see:
- “Your message could not be sent. Please reload the page and try again.” – formconfirmed did not let the submission through (flagged or blocked).
- “Your message could not be checked right now. Please try again in a few minutes.” – no clear answer from the service, and the backup check was off or did not pass.
When no copy is kept
No copy is kept under “Held messages” if 200 messages were already stored within 24 hours, 2,000 are stored in total (messages passed on count until they are deleted after 14 days), the database lock is not free within one second, the database reports an error, or no usable fields are left. If the formexposed plugin is active and its quarantine reports that it is ready, formconfirmed tries to store the copy there instead of under “Held messages”. A copy is only kept there if the quarantine is available, holds fewer than 2,000 entries and its write succeeds; the plugin's own storage also only counts when the write succeeds.
Setup
- Open Settings → formconfirmed → “Forms”.
- In the “Fluent Forms” section, turn on “Protect”. If it says “Not installed”, formconfirmed does not detect Fluent Forms.
- The table lists your Fluent Forms forms. Turn on the ones you want under “Protected”. “Edit” opens a form in the Fluent Forms editor. Forms not yet switched individually follow “Protect new forms automatically”.
- Click “Save forms” and then clear the page cache and CDN, if any.
- Optional: under “Field mapping”, set “Automatic”, “Name”, “Email”, “Message” or “Ignore” per field. Name and message are only sent with “Check names and message text”.
Check your own notification first
- Open the form in the Fluent Forms editor.
- Open “Settings & Integrations” → “Email Notifications”.
- Check that the notification (e.g. “Admin Notification Email”) is switched on and goes to an address you read.
Before testing: note the starting point
- Note the counters under “Since activation” and the time of “Last answer of the service” in “Overview”. The counters cover the whole site; test when nobody else is likely to send forms.
Harmless test
- Open the page with the form in a private browser window without being logged in.
- Developer tools (Elements): the form should contain an element
fcp-widgetand, once loaded, a hidden fieldfcp-responseinside it. For multi-step forms, check this on the last step. - Send a short, normal message without links, using an address you read. For multi-step forms, go through all steps.
- Expected: your Fluent Forms confirmation appears, the entry is listed under “Entries”, the notification arrives.
- Compare “Overview” with your notes. A higher “allowed” counter suggests a check – but on a busy site it may have been another submission. An unchanged counter, however, does not prove missing protection: the counters are read without a lock and saved as a whole, simultaneous submissions can overwrite each other, and a failed save is not reported. In that case check the switches, the
fcp-widgetelement and the result in the form again. - If you see one of the two messages above, formconfirmed did not let the submission through. Then check “Held messages” (column “Why”) in case a copy exists there.
What indicators prove – and what they do not
| Indicator | Means | Does not mean |
|---|---|---|
| Fluent Forms confirmation | formconfirmed refused nothing. | That a check happened: it also appears without protection. A higher “allowed” counter suggests a check, but it covers the whole site. |
| “Test the connection”: “Connected: …” | The service answers and accepts the secret key. | That a form is protected or that messages arrive. |
| “Backup check: self-test passed.” | The backup check solved its own task. | That visitors can fetch the task: it also counts as passed when the internal request to admin-ajax.php (action formconfirmed_pow) ends with a network error or HTTP 401. |
| Counter “held for review” | How often “hold” was decided (with Fluent Forms the visitor still sees an error). | That a copy was stored: the counter goes up before the storage attempt. |
| Counter “refused (a copy is kept)” | How often a submission was refused. | That a copy exists: storage can fail at its limits. |
| Badge visible | The widget has loaded and the service displays the badge. | That your server checked the submission. |
| No badge | – | Missing protection: paid plans can hide the badge. Check fcp-widget and the counters. |
Getting a refused message back
- If a copy exists under “Held messages”: “Send” passes it to the Administration Email Address (can be changed with a filter), not to the recipients of your Fluent Forms notification. “Passed to mailer” does not confirm delivery.
- “Not spam” on a message under “Held messages” sends only its check ID and your rating to formconfirmed.
- If there is no copy, Fluent Forms did not save the submission; ask the person to try again.
Troubleshooting
| What you see | Possible cause | What to do |
|---|---|---|
| “Fluent Forms” shows “Not installed” | Fluent Forms is not active. | Activate Fluent Forms. |
No fcp-widget in the form | Form or section off, not saved, page served from cache. | Check the switches, “Save forms”, clear the cache; see cache and conflict help. |
No fcp-widget in a multi-step form | The helper script was delayed, combined or not loaded (not tested). | Exclude …/plugins/formconfirmed/assets/js/forms.js, …/assets/js/backup.js, https://formconfirmed.com/v1/widget.js and the inline scripts formconfirmedForms/formconfirmedBackup from “delay”/“combine”; reversible. |
| Unclear whether a conversational form is checked | Form type not mentioned in the code; an unchanged counter alone proves nothing. | Check on a test page, ask the operator, or use a normal form. |
| Error from Fluent Forms itself (e.g. reCAPTCHA, honeypot) | Another protection refused first; formconfirmed was not asked. | Check that protection's settings; do not switch it off wholesale. |
| “…could not be checked right now…” | No clear answer from the service, backup check off or not passed. | Read the notice in “Overview”, run “Test the connection”, check “Backup check on this site”. |
| “…could not be sent…” for a normal message | Submission flagged or blocked. | Look at “Held messages” (column “Why”) if a copy exists there; test with plain text; use “Not spam” if appropriate. |
| Confirmation and entry present, but no email | formconfirmed refused nothing; the problem is further down the chain. | Check “Email Notifications” and WordPress mail delivery. |
Limits
- Not tested: multi-step forms, conversational forms, partial entries, payment forms, forms in popups, position of the error message. Check such forms on a test page before relying on them. Do not switch protection off wholesale when something goes wrong.
Formidable Forms
Enable detected Formidable forms individually in the formconfirmed Forms tab.
- Select the required form switch and check the setting for future forms.
- Test the published page with normal synthetic data. Compare the formconfirmed result, the Formidable entry and the actual notification.
- The adapter adds a validation error for submissions it does not pass. Check the appropriate storage for a possible review copy without assuming a copy or delivery exists.
Limits: Multipage forms may validate while advancing between pages: check that a single-use token is not consumed too early. Frontend entry editing, drafts and payment workflows also need separate tests.
Check your own workflow
Start on your own test installation with synthetic data and a notification channel you control. Check a normal submission, the actual protection result and the notification separately. A browser confirmation or successful connection test does not prove delivery. Run spam counterexamples only in your own test environment.
Comments, registration and login
Comments
The adapter covers the theme's normal comment form through wp-comments-post.php. An explicit block is refused with an error page; hold sends the comment to moderation and reject treats it as spam. This does not cover REST, XML-RPC or pingbacks. The check is skipped for logged-in comment moderators.
Registration
WordPress registration through wp-login.php and WooCommerce registration under My account have separate switches. Registrations that are not passed are refused; this does not create a guaranteed review copy or an account awaiting moderation. Multisite signup and account creation at WooCommerce checkout are not promised by these two adapters. Test such workflows only with test accounts and a local mail catcher.
Login — optional
WordPress login protection is off by default. Enable it on a test installation first and retain an independent recovery path. Only a login with an already successful password check on the normal wp-login.php page receives this additional check: an explicit block stops it; flag or an unclear service response does not replace password verification. This is the WordPress plugin's contract, not the formconfirmed account login's contract. SSO, two-factor plugins and alternative login pages need separate tests.
Narrow down cache and plugin conflicts
The badge is missing
- First check activation, the connection and the correct form switch; paid accounts can hide the badge. Judge protection by an actual verification result, not the badge alone.
- Open the published page while logged out and check script-loading errors in your own browser. Clear only the affected page/plugin caches and test again.
Old settings or delayed JavaScript
- Save the correct form selection and clear the relevant cache layers. Change one optimization setting at a time on a test installation.
- If needed, exclude only the affected widget/helper script from delay or minification. Do not broadly allow admin-ajax.php, all scripts or external destinations.
A duplicate widget or a plugin conflict
- Check whether both an automatically inserted widget and a manual form tag are present. Remove only the confirmed duplicate on the test installation.
- When formexposed is also installed, account for its form-protection/quarantine integration. Do not disable protection across the production website.
The check passed, but no notification arrived
- Separate formconfirmed approval, form processing and mail delivery. Check the configured recipient, plugin notifications and your own mail channel.
- For held contact messages, check the responsible storage. The plugin's own quarantine admits at most 200 per day and 2000 entries in total; active formexposed may use its own quarantine. Registration and login are never copied there.
The service or connection is unavailable
- Check connection status and fix a confirmed key, domain or network configuration issue without copying keys into screenshots or support messages.
- Contact forms and comments can pass only after a successful independent backup check; otherwise the adapter's own behavior applies. Registration and login have the special rules above. An unclear response guarantees neither delivery nor a stored copy.
Integrations and available evidence
This table reads the available adapters from the plugin ZIP currently offered here. It is a source inspection, not a version or functional test of your WordPress combination. An aggregate WordPress status does not replace individual evidence covering provider, version, form type and test date.
| Integration | Selection in the plugin | Evidence |
|---|---|---|
| Contact Form 7 | Individual forms in the Forms tab | Adapter present in the offered ZIP; test your own combination. |
| WPForms | Individual forms in the Forms tab | Adapter present in the offered ZIP; test your own combination. |
| Gravity Forms | Individual forms in the Forms tab | Adapter present in the offered ZIP; test your own combination. |
| Elementor Pro | One switch for this area | Adapter present in the offered ZIP; test your own combination. |
| Fluent Forms | Individual forms in the Forms tab | Adapter present in the offered ZIP; test your own combination. |
| Formidable Forms | Individual forms in the Forms tab | Adapter present in the offered ZIP; test your own combination. |
| WordPress comments | One switch for this area | Adapter present in the offered ZIP; test your own combination. |
| WordPress registration | One switch for this area | Adapter present in the offered ZIP; test your own combination. |
| WooCommerce registration | One switch for this area | Adapter present in the offered ZIP; test your own combination. |
| WordPress login | One switch for this area | Adapter present in the offered ZIP; test your own combination. |
About the offered ZIP
- Plugin version
- 1.6.1
- File size in bytes
- 62427
- SHA-256
55fc93b56d3feadaa61fb123514a20c4cd2d554232876b8e4e1a5b8ce3e023e2
Minimum requirements declared by the plugin: WordPress 6.2 / PHP 7.4
Original changelog from the ZIP (English)
- Quarantine counts use fresh WordPress queries and reject admission when storage cannot be checked. Cleanup diagnostics retain a failed count even when the following oldest-entry lookup succeeds.
- Admin input handling, translation context and uninstall cleanup have been tightened; connection, technical report and feedback data flows are documented together.
- Held messages: the explanation of the 14-day quarantine now stands above the filters instead of below the list header.
- Field mapping: the role selector is wide enough for its longest choice.
These details come from the local ZIP offered here. Compare its SHA-256 checksum with your fully downloaded file. Test updates on a test installation first; a hash is not a digital signature.