Anti-spam, Spam protection, ReCaptcha for all forms and GDPR-compliant

1. The problem occasionally occurs right after installation due to caching. In such cases, the necessary JavaScript for proof-of-work isn't loaded as intended. To resolve this, clear the cache on your webserver (WordPress caching is typically managed by plugins, which offer an option to clear the cache) and in your browser.
2. JavaScript might crash due to incompatibility between this plugin and another one you're using. If you notice this, please report it to me. I usually address such issues within the same day. Additionally, it's crucial to ensure that JavaScript is functioning correctly on all your pages, even without this plugin. In most browsers, you can identify JavaScript errors by pressing F12 on your page and navigating to the console. Here, you can observe what's happening on your page.
3. Generally, I recommend running the plugin in Explicit mode 🎯 as it's more efficient and avoids compatibility problems. Please refer to the "help" section for this option.

1. Activate the Analysis mode 🔍,
2. Submit the form and look for the message that has been saved for the new submission in the Analytic Box
3. Open the message and enhance the scope of the spam to this type of message
4. If the message doesn't appear here, or is already in scope, please give me a note In general I recommend to run the plugin in the Explicit mode 🎯 and to do so with all types of submissions that you which to be considered for the spam check.

If you face problems with the activation of Jetpack this may occur during the handshake-procedure of jetpack. This procedure acts like a bot, when it passes a passphrase from a certain IP adress to an automatically generated form on your site. In order to get this fixed, you need either to disable the option 🖥️ Apply on REST-API, or to whitelist the respective form that is used to exchange the passphrase. Usually you need to process the following steps for whitelisting: 8. Check the spam folder for the respective message that has been blocked 9. Copy the site-adress "from_site" 10. Paste the site-adress into the option 📄 Site-Whitelist on the properties site 11. Press save Usually you need to whitelist two different sites to connect jetpack: 12. To connect the site: your-domnain-without-protocol/?rest_route=/jetpack/v4/verify_registration/ 13. To connect your user: your-domnain-without-protocol/?rest_route=/jetpack/v4/remote_authorize/ Generally, I recommend running the plugin in Explicit mode 🎯 as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option.

If you face problems with other plugins (i.e. during plugin installation/ activation) this may occur during handshake-procedures, or during maintenance of your plugin from the vendor. These procedures usually act like bots, as they pass a code or contents via certain automatically generated forms on your site. In order to get this fixed you can either disable the option 🖥️ Apply on REST-API, or whitelist the IP address of your vendor, or you can whitelist the page which contains the maintenance form. In order to check whether such a problem occurs you can check the spam folder of this plugin. Here you find the site adress that you can use for whitelisting as "from_site" too Generally, I recommend running the plugin in Explicit mode 🎯 as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option.

You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option 📄 Site-Whitelist. Do not forget to cut the protocoll (i.e. "http" and "https"). Note: As Thrive doesn't use the standard WordPress-REST-route, just deactivating the option 🖥️ Apply on REST-API will not work. Generally, I recommend running the plugin in Explicit mode 🎯 as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option.

You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option 📄 Site-Whitelist. Do not forget to cut the protocoll (i.e. "http" and "https"). Alternatively you can deactivate the option 🖥️ Apply on REST-API if your services is using the standard WordPress-REST route. Generally, I recommend running the plugin in Explicit mode 🎯 as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option.

When you use the Borlabs Script Blocker to scan for JavaScripts, the scan doesn't work properly, as it doesn't show any JavaScripts. Just deactivate this plugin for the scan and activate it again after the scan.

1. Important messages could be shown in browser console (F12) on problematic page
2. Whenever you post something to the support forum, try to hand over all details
3. If the recaptcha doesn't work on any form, give me a notice and I will try to fix that

• Use standard WordPress plugins page for deactivation and deletion of the plugin
• When deactivating the plugin you will be asked for the reason. If you face any problems I would be glad if you report to it me as detailed as possible. Usually I will fix them quickly. If you give me contcat details, I may inform you as soon as it is fixed.