Troubleshooting Tech Dragon Divi Turnstile Nexus
Use this guide for the most common configuration, visibility, submission, and compatibility problems.
Turnstile does not appear
Check:
- Tech Dragon Divi Turnstile Nexus is active.
- Valid credentials are saved.
- The specific form is explicitly configured to use Turnstile.
- The form is a supported Contact Form or Email Optin surface.
- You are testing the published page, not only a builder preview.
If the page has no Turnstile-protected forms, the plugin does not load Turnstile unnecessarily.
Credentials are saved but not verified
Saved and verified are separate states.
Run Settings → Tech Dragon Divi Turnstile Nexus → Verify Turnstile connection.
If verification fails, confirm:
- the site and secret keys belong to the same Cloudflare Turnstile widget;
- the correct hostname is configured in Cloudflare;
- your site can connect to Cloudflare; and
- the copied credentials do not contain extra characters.
The secret field looks blank after saving
This is expected. The saved secret is not repopulated into the browser.
If the page indicates a secret is configured, leaving the secret field blank when saving preserves it. Use the removal control only when intentionally deleting it.
Bulk enable is not available
Bulk enable requires a successfully verified Turnstile configuration and at least one eligible existing form.
If no eligible forms are detected, there may be nothing for the action to change.
Bulk enable skipped some forms
The plugin skips forms it cannot safely identify or update.
Review the protection inventory for the state of each detected form.
A new form is unprotected
This is expected. New supported forms default to Turnstile OFF.
Open the module's Spam Protection settings and select Turnstile explicitly.
Form submits but email does not arrive
Turnstile only controls whether the protected action is allowed to proceed.
After Turnstile succeeds, troubleshoot Divi's email configuration, WordPress mail delivery, or SMTP.
Form submits but Email Optin does not subscribe
Check the account, list or audience, and other Email Optin settings in Divi. Turnstile verifies the visitor; it does not replace the email-marketing service connection.
The public page and visual builder behave differently
Use the published page for final testing. A form can behave differently in the Visual Builder than it does for a real visitor.
One form works and another does not
Each protected form should work independently.
Confirm both forms are independently configured. If one form resets or affects another, collect the page layout, form types, Divi version, and plugin version.
Divi 5 shows an unsupported legacy Divi 4 form
This is expected.
Tech Dragon Divi Turnstile Nexus 1.2.0 supports native Divi 5 Contact Form and Email Optin modules. It does not support legacy Divi 4 Contact Form or Email Optin modules embedded inside Divi 5.
Rebuild or migrate the affected form as a native Divi 5 module.
A Theme Builder form is missing from inventory
The protection inventory checks supported forms in regular Divi content and relevant Theme Builder layouts. If a supported form is missing, note which Theme Builder template or layout contains it, along with the form type and plugin version, when contacting support.
What to collect for support
Provide:
- WordPress version
- PHP version
- Divi version
- Tech Dragon Divi Turnstile Nexus version
- whether a Divi child theme is active
- form type
- whether the form is in page content or Theme Builder
- whether the form appears as protected, unprotected, or unsupported in the inventory
- whether configuration verification succeeds
- a concise description of the failure
Do not send:
- the Cloudflare secret key
- raw verification tokens
- passwords
- private API credentials
- sensitive form submissions