Spam protection, anti-spam, firewall, premium plugin. No spam comments & users, no spam contact form & WooCommerce anti-spam.
Top-rated anti-spam protection for WordPress. No CAPTCHA, no questions, no animal counting, no puzzles, no math and no spam bots. Universal AntiSpam plugin.
CleanTalk is an anti-spam plugin which works with the premium Cloud Anti-Spam service cleantalk.org. This plugin as a service https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#6-software-as-a-service-is-permitted
It’s more than just a tool to combat spam; it’s an integral component that enhances the overall quality and performance of your website.
techbusinessnews.com.auImprove Your Security WordPress Spam Protection With CleanTalk Anti-Spam
The Hacker News.CleanTalk – Cloud-Based Anti-Spam Service to Keep Your Site Bot-Free.
NewsWatch Review.Compare reCAPTCHA & Akismet VS CleanTalk
https://www.saashub.com/compare-recaptcha-vs-cleantalk
https://www.saashub.com/compare-akismet-vs-cleantalkI know you have heard of a number of anti-spam plugins. But you must know, the cloud-based ones are the best regarding detection rate. They compare all the content in forms with their own algorithm to find out the legibility.
www.techwibe.comThe key selling point of CleanTalk for me is not simply its effectiveness. It’s the fact that CleanTalk works in the background. It does not make users jump through hoops in order to submit a comment or complete a form.
www.kevinmuldoon.com
Native spam protection for WordPress, JetPack comments and any other comment plugins. The plugin moves spam comments to SPAM folder or you can set the option to ban spam comments silently. You can also enable the option in the plugin settings to auto-delete comments from SPAM folder.
Plugin extends Contact Form by WPForms to provide spam protection. It filters spam submissions for each type of forms – simple contact form, marketing form, request a quote and etc.
Plugin extends spam protection for Elementor Website Builder. It filters spam submisssions and tested for contact form type.
Plugin extends spam protection for Gravity forms. It filters spam submisssions for any type of forms.
Plugin extends spam protection for Formidable Form Builder. It filters spam submisssions for any type of forms – Contact Form, Survey & Quiz Forms.
Plugin extends spam protection for Contact Form 7 (CF7). It can be used with any other third-party spam filters.
How to protect your Contact Form 7 using CleanTalk Anti-Spam plugin
Anti-spam by CleanTalk filters spam registrations and spam reviews for WooCommerce. The plugin is fully compatible with WooCommerce 2.1 and higher.
The plugin blocks spam emails via any theme (built-in ones included) contact forms. The plugin filters spam emails silently (without any error notices on WordPress frontend) in AJAX forms as well.
Spam protection for everything about bbPress: logins, registrations, forums, topics and replies.
With the help of anti-spam by CleanTalk you can inspect through existing comments to find and quickly delete spam comments at once. To use this function, go to WP Console -> Comments -> Find spam comments.
With the help of anti-spam by CleanTalk you can inspect through existing accounts to find and quickly delete spam users at once. For use this function, go to WP Console -> Users -> Check for spam. Also, you can export a list of spam users to the CSV.
Automatically block comments and registrations from your private black IP/email address list.
This option hides the «Website» field from standard WordPress comments forms. After that spammers won’t be able to send spam links using «Website» field in the bottom of the comments form.
This plugin uses multiple anti-spam tests to filter spam bots having as low false/positive rate as possible.
So, you already know that the speed of the site has a direct impact on SEO.
CleanTalk works faster than most of the other anti-spam plugins. It is common knowledge that the faster your site loads, the better your customer experience is, the better your SEO will be, and the better your site will convert. Speed is becoming increasingly important in SEO, conversion and user experience. Today, site speed is one of the most important ranking factors on Google. A site that loads slowly will lose visitors and potential revenue.
Among anti-spam plugins CleanTalk AntiSpam is one of the fastest. Despite the large plugin functionality, the developers have optimized the performance of
the plugin so that AntiSpam by CleanTalk is faster than most analogs. This contributes to the cloud service architecture, as all calculations take place in the cloud, not on the server, the server receives the finished result for further action.
https://s.w.org/plugins/cleantalk-spam-protect/screenshot-5.png?r=1288723
Unlike stand-alone plugins (WP Armour, Antispam Bee, WP Cerber) Anti-Spam by CleanTalk uses less CPU that improves site response, visitors experience and SEO results.
Spam FireWall allows blocking the most active spam bots before they get access to your website. It prevents spam bots from loading website pages so your web server doesn’t have to perform all scripts on these pages. Also it prevents scanning of pages of the website by spam bots. Therefore Spam FireWall significantly reduces the load on your web server. Spam FireWall also makes CleanTalk the two-step protection from spam bots. Spam FireWall is the first step and it blocks the most active spam bots. CleanTalk Anti-Spam is the second step and checks all other requests on the website in the moment of submitting comments/registers etc.
All the CleanTalk Spam FireWall activity is being logged in the process of filtering.
Spam FireWall: Anti-Flood and Anti-Crawler options are intended for blocking unwanted bots, content parsing, shop goods prices parsing or aggressive website scanning bots. Learn more https://cleantalk.org/help/anti-flood-and-anti-crawler
CleanTalk is an all-in-one anti-spam solution for WordPress that protects login, comment, contact and WooCommerce forms at once. You don’t need to install separate antispam plugins for each form. It allows your blog to work faster and save resources.
CleanTalk is a transparent antispam tool, we provide detailed stats of all incoming comments and logins. You can always be sure that there are no errors. We have developed a mobile app for you to see antispam stats wherever you want.
We have developed the antispam for WordPress that protects you from spam bots at the maximum level allowing you to provide your visitors a simple and convenient form of comments/registrations without annoying CAPTCHAs and puzzles. CleanTalk detects spam in multistage tests allowing us to block up to 99.998% of spam bots. The anti-spam method offered by CleanTalk avoids inconvenient for communication methods (CAPTCHA, question-answer etc.), and offers to your site visitors a more comfortable one.
CleanTalk is a premium anti-spam service for WordPress, the plugin works with our own CleanTalk Cloud Service. Anti Spam by CleanTalk offers a free trial, you can look at the pricing here. We provide anti-spam services at the highest level. To maintain this level we cannot afford to offer a free version of our service, as this will immediately affect the quality of the providing anti-spam protection. Paying for a year of anti-spam service, you save a lot more and receive:
The most popular anti-spam method is CAPTCHA – the annoying picture with curved and sloping symbols, which are presented to the visitor to decipher and fill in. In is supposed that spam bots won’t discern these CAPTCHA, but a visitor will. CAPTCHA provokes great irritation, but if the visitor wants to comment, he has to fill in these symbols time after time, making mistakes and starting once again. Sometimes CAPTCHA reminds us of the doodles of a two year old child. For users with vision problems CAPTCHA is an insurmountable obstacle. Users hate captcha. Captcha for users means “hate”. Unreadable CAPTCHA stops about 80% of site visitors. After 2 failed attempts to decipher CAPTCHA 95% of visitors reject further attempts. At the sight of CAPTCHA and after input errors, many visitors leave the resource. Thus, CAPTCHA helps to protect the resource spam both from bots and visitors. CAPTCHA is not a panacea from spam. Doubts concerning the Need for CAPTCHA?
“Ultimately, CAPTCHAs are useless for spam because they’re designed to tell you if someone is ‘human’ or not, but not whether something is spam or not.” Matt Mullenweg
You do not have to work in IT to know what spam is. Besides piles of unwanted email, there are spam bots, or special software programs designed to act as human website visitors that post unwelcome messages over the Internet to advertise dubious services. More often than not spam messages do not even make sense. Similar to bacteria and virus mutations developing antibiotic resistance, spam bots are becoming more resilient in penetrating Internet firewalls and security layers.
To switch the plugin work in the white-label mode you should set up a few settings on your main site in WordPress Multisite Network:
The plugin will do everything rest.
It is very important to be sure that the user used his real email address. Spambots very often use fake email addresses, i.e. which addresses do not exist.
CleanTalk will check email addresses for existence in real time.
Non-existing email addresses also entail several other problems for website owners.
Improve your email list with email validation without fake emails.
Block fake and suspicious users with disposable & temporary emails to improve email delivery. So, it also prevents malicious activity, spam bots, and internet trolls.
Spam bots can use your search form to make a GET request with spam text. CleanTalk Anti-Spam has the option to protect your website search form from spam bots. Each time, the search generates a new page and if there are many requests, this can create additional load. So, under some conditions, spam searches can be indexed, which affects SEO,
You will always know what users were looking for on your site.
This option disables comments on your site. You can choose one or several options:
When using Disables comments, existing comments will not be deleted and will remain on the pages.
CleanTalk Anti-Spam offers a feature called “Encode contact data” that is designed to encode all email addresses on the website pages. Encoding the email addresses increases the level of protection of contact data from being abused, parsed, getting spammed and used in spam mailing lists by bots and online criminals. To reveal the encoded email address simply click on it and it will be decoded instantly.
Yes, it will. The Anti-spam by CleanTalk is compatible with any WordPress theme.
CleanTalk stops up to 99.998% of spam bots, so you can disable other anti-spam plugins (especially CAPTCHA-type anti-spam plugins). In some cases several anti-spam plugins could conflict with each other, so it would be …
Download, install and activate ‘Anti-spam by CleanTalk’.
Get Access key https://cleantalk.org/register
Enter Access key in the settings: WordPress console -> Settings -> Antispam by CleanTalk
Do dummy spam comment (registration or contact message) with email [email protected]. You should see notice: Forbidden. Sender blacklisted.
Done! The plugin is ready to use.
Important! To test spam protection you must post a dummy submissions as website visitor (use must logged out from WordPress console), because the plugin doesn’t filter submissions from WordPress administrators.
In WordPress multisite version you can switch the plugin to use Global Access key. In this way the plugin doesn’t show any options to enter Access key in plugin settings and doesn’t show Trial banner in WordPress backend. To setup global CleanTalk access key for all websites in WPMS, define constant in your wp-config.php file before defining database constants:
define('CLEANTALK_ACCESS_KEY', 'place your key here');
Make it before you activated the plugin. If the plugin already activated, deactivate it and add the code and active it again.
Now, all subsites will have this access key.
Go to Dashboard at the cleantalk.org or use Android, iPhone anti-spam app to manage and control spam protection.
AntiSpam settings are easy to use to protect any contact forms. For example - Ninja forms, Fluent forms and etc.
AntiSpam plugin rejected a spam bot at the CAPTCHA less registration form. The plugin provides explanation to visitor and websites about each rejected comment/registration or contact message.
Use AntiSpam analytics tool for each website in service Dashboard to have information about spam/legitimate stats.
Use AntiSpam log to control anti-spam plugin.
CleanTalk works faster than most of other anti-spam plugins.
The Dashboard with a map of most spam active countries per your account.
The plugin deletes/removes the existing spam comments and users accounts.
CleanTalk's dashboard update link.
CleanTalk's dashboard.
SpamFireWall log.
Spammers want to get backlinks from your site to improve their site’s PageRank or redirect your visitors to malicious sites.This level of spam can damage your reputation with readers and commentators if you fail to tackle it. It is not uncommon for some WordPress websites to receive hundreds or even thousands of comments every week. However, by using a CleanTalk plugin, spam can be easily handled by your WordPress website.
Yes, it is. The plugin doesn’t block mobile visitors as well as desktop website visitors. It uses several independent anti-spam tests to decrease the number of false outcomes and to have as low false-positive rate as possible. Multiple anti-spam tests help to avoid false/positive blocks for real website visitors even if one of the tests failed.
Spam comments are being moved to SPAM folder by default or you can set the option to ban spam comments silently.
Please use the email [email protected] for comments, contacts or signups to see how the anti-spam protection works. Also, you can see the logs for the last 7 days in the Dashboard or look at the folder “Spam” for banned comments.
Please, note – administrator’s actions are NOT being checked.
The plugin uses several simple tests to stop spammers:
The plugin passes pingbacks without any checks by default. All trackbacks will be blocked if the sender had spam activity.
Yes, you can. The plugin has the option to test all pending comments via database of spam active IP/Email, found spam comments will be moved to Trash folder.
The plugin checks all non-spam comments in the blacklist database and shows you those senders who have spam activity on other websites.
There are some differences between blacklist database and API to protect you from spam bot registrations/comments online. Blacklists show all history of spam activity, but our API (which is used in spam tests) relies on other parameters too: last day of activity, number of spam attacks during the last days etc. These mechanisms help us to reduce the number of false outcomes. So, there is nothing strange, if some emails/IPs are not found by bulk comments/accounts test.
To check comments please go here:
WordPress console -> Comments -> Find spam comments
To check users please go here:
WordPress console -> Users -> Find spam users
Yes, the plugin is compatible with WordPress MultiUser. Each blog in multisite environment has individual anti-spam options for the protection from spam bots.
There are a few reasons for this:
The plugin has several options to detect spam bots and humans. If you just post spammy text like this:
"I want to sell something", "Buy something here.." and etc
the comments will be passed, because the plugin detects sender as a human. So, use special email [email protected] to test the anti-spam functionality or wait a few days to see how the plugin works.
The plugin is free and distributed under the GPLv2 license.
CleanTalk anti-spam plugin works with a cloud base anti-spam service and this plugin is a Software as a service (SaaS).
CleanTalk it’s a free plugin that works with premium Cloud Anti-Spam service.
https://en.wikipedia.org/wiki/Software_as_a_service
The fact that the plugin works with a premium type service is mentioned in the plugin annotation and in its WordPress catalog description.
We are ready to help you with any issue regarding CleanTalk. There are hundreds of environment compositions and we do our best to cover as many as possible.
Anti-spam by CleanTalk doesn’t use static HTML code in its templates, so all anti-spam functions work correctly with any WordPress cache plugins.
Yes, it does. Plugin protects web-forms on your websites which send data to third-party servers (like MailChimp). To enable this protection set the option ‘Protect external forms’ in the plugin settings.
CleanTalk is fully compatible with CloudFlare. Service doesn’t filter CloudFlares IP’s (AS13335) through blacklists database, so in this case plugin/service filters spam bots using other anti-spam tests.
Yes, it is. CleanTalk works with any CDN system, i.e. CloudFlare, MaxCDN, Akamai.
Yes, you can. Just use following snippet:
<?php if(!function_exists('ct_test_message')){ include_once( ABSPATH . '/wp-content/plugins/cleantalk-spam-protect/cleantalk.php' ); } //for registration test: $res=ct_test_registration("nickname", "[email protected]", "127.0.0.1"); //or for some other messages (contact forms, comments etc.) $res=ct_test_message("nickname", "[email protected]", "127.0.0.1", "test message");
$res now contents array with two parameters:
* $res[‘allow’] – is request allowed (1) or not (0)
* $res[‘comment’] – comment for our server’s decision.
This script is used for AJAX JavaScript checking. Different themes use different mechanisms of loading, so we use two methods for loading our script. If you absolutely know what you are doing, you can switch one of the methods off by defining constants in your wp-config.php file:
define('CLEANTALK_AJAX_USE_BUFFER', false); //false - don't use output buffering to include AJAX script, true - use it
or
define('CLEANTALK_AJAX_USE_FOOTER_HEADER', false); //false - don't use wp_footer() and wp_header() for including AJAX script, true - use it
Yes, you can. There is a special setting in plugin settings.
You could use this guide to learn more: https://cleantalk.org/help/exclusion-from-anti-spam-checking#wordpress
Yes, you can exclude your data. There is a special setting in plugin settings.
You could use this guide to learn more: https://cleantalk.org/help/exclusion-from-anti-spam-checking#WordPress_field_exclusions
Use special IP 10.10.10.10 in URL to test Spam FireWall. For example,
https://cleantalk.org/blog/?sfw_test_ip=10.10.10.10
Attention! The incognito mode should be enabled in your browser when you do a test. To enable incognito mode press Ctrl+Shift+N for Chrome, Opera и Safari browsers; press Ctrl+Shift+P for Firefox, Internet Explorer and Microsoft Edge. A full guide to enable Incognito mode is here: https://www.wikihow.com/Activate-Incognito-Mode
To set up global CleanTalk access key for all websites in WPMU, define constant in your wp-config.php file before defining database constants:
define('CLEANTALK_ACCESS_KEY', 'place your key here');
Now, all subsites will have this access key.
CleanTalk works with Varnish, it protects WordPress against spam, but by default the plugin generates a few cookies for the protection from spam bots and it also disables Varnish cache on pages where CleanTalk’s cookies have been stored. To get rid of the issue with cache turn off the option ‘Set cookies’ in the plugin settings.
WordPress console -> Settings -> CleanTalk -> Advanced settings
Now the plugin will protect WordPress comments, registrations and most of popular contact forms, but will not protect some of rarely used contact forms.
Yes, it does. But you have to turn off the SpamFireWall and the option ‘Use AJAX for JavaScript check’ in Advanced settigns of the plugin to be fully compatible with Accelerated Mobile Pages.
No. You don’t need to change anything in the plugin’s settings or in your CleanTalk Dashboard. The plugin will work regardless of the protocol.
Anti-Spam – will blocks users from selected IP or network from using contacts/messages/registrations/comments forms.
Spam FireWall – will blocks users from selected IP or network from entering the website.
Please, read more here
https://cleantalk.org/help/sfw-blocks-networks
By default, all spam comments are placed in the spam folder, now you can change the way the plugin deals with spam comments:
You can prevent the proliferation of Spam folder. It can be cleaned automatically using the option “Keep spam comments for 15 days.” Enable this option in the settings of the plugin: WordPress Admin Page -> Settings -> Antispam by CleanTalk -> Advanced settings -> enable “Keep spam comments for 15 days” -> Save Changes.
Move to Trash. All spam comments will be placed to the folder “Trash” in the WordPress Comments section except comments with Stop-Words. Stop-Word comments will be always stored in the “Pending” folder.
Ban comments without moving to WordPress backend. All spam comments will be deleted permanently without going to the WordPress backend except comments with Stop-Words. Stop-Word comments will be always stored in the “Pending” folder.
What comments were blocked and banned can be seen in the Anti-Spam Log here: https://cleantalk.org/my/show_requests?int=week
To manage the actions with spam comments, go to the Control Panel, select the website you want to change the actions for and go to “Settings” under the name of the website.
Please, read more here:
https://cleantalk.org/help/spam-comment-management
Yes, it is. Please read this article,
https://cleantalk.org/publicoffer#cleantalk_gdpr_compliance
= 6.36 Jul 11 2024
* New. Integration. Kulahub.
* New. Integrations. Added eloqua handler.
* New. Integration. Piotnet (PAFE) forms.
* New. Integration. Kadence Blocks Advanced.
* New. Settings. W3 Total Cache settings adjusting implemented.
* Upd. API. Method send_feedback upgraded to the version api3.0.
* Upd. Settings. Updated debug view.
* Upd. Settings. WL mode for WPMS link updated.
* Upd. The Real Person feature. Badge layout and popup improved.
* Fix. AltSessions. Encode array to JSON if tried to write raw array to the database.
* Fix. EmailEncoder. Added hook to encode.
* Fix. Forced AltCookies. Bot detector token gain improved.
* Fix. Integration. MailChimp and MailChimp Premium. Empty page issues on CleanTalk response fixed.
* Fix. Integration. Monta Checkout service action excluded.
* Fix. Integration. Ajax search lite plugin request was excluded – it will be caught by standard search form protection.
* Fix. Integration. Bloom integration fixed.
* Fix. Integration. WSFroms. Pregmatch issue fixed.
* Fix. Pixel. Pixel URL fixed.
* Fix. Request. WP HTTP API. Prepare headers to Request::flatten before request.
* Fix. SFW. SFW updating fixed.
* Fix. Server variables. Special sanitize rule for site search cases.
= 6.35 Jun 27 2024
* New. Comments. RealUserBadge implemented.
* New. Code. LinkConstructor class.
* New. Integrations. Added handler for LearnPress.
* New. Integration. Paid Membership Pro direct integration implemented.
* Mod. Links. CleanTalk links have UTM data now.
* Mod. RequestParameters. Common storage implemented.
* Mod. Cookies. Param ‘apbct_urls’ now works via RequestParameters class.
* Mod. Index files added to the plugins structure.
* Ref. Integrations. Updated flow for force_ajax_check.
* Fix. AltSessions. Encode array to JSON if tried to write raw array to the database.
* Fix. JS. External forms. Search for a submit element.
* Fix. Admin dashboard. Links to get premium layout fixed.
* Fix. JS. Replacing the DOM reference with a variable.
* Fix. JS. Delete xhr started from log.
* Fix. Settings. Get key automatically. Timezone fixed.
* Fix. Integrations. CF7.
* Fix. Integrations. ZOHO.
* Fix. integrations. WS forms. Email provided for get fields any.
= 6.34 Jun 13 2024
* Fix. Pixel. Added nofollow attribute.
* Upd. Admin Bar structure. Renewal links conditions fixed. Code refactored.
* Upd. Settings. Email encoder A/B testing.
* Upd. Public JS localization. Now can be selected.
= 6.33.2 Jun 01 2024
* Fix. Admin notices. Purchasing the product page link fixed.
= 6.33.1 May 31 2024
* Fix. Admin panel. Banners. Renewal payment links getting fixed and refactored.
= 6.33 May 30 2024
* New. Integrations. Flamingo integration implemented.
* New. Integrations. Added handler for learnpress signup.
* New. Intergations. Proto theme login popup protected.
* Upd. Woocommerce. Uni CPO plugin. Clear service fields improved for premium version.
* Fix. Woocommerce. Exclude hubspot integration as external form on WooCommerce checkout.
* Fix. Woocommerce. Uni CPO plugin. Clear service fields from post.
* Fix. GetFieldsAny. Get the very first email to the process. Provide additional email addresses on the form to the request message.
* Fix. CleanTalk Public. Protect LearPress registration process on plugins_loaded hook.
* Fix. JS. External Forms. Exclude elementor search form from external forms pre-handling.
= 6.32.1 May 20 2024
* Fix. JS. Function apbctCatchXmlHttpRequest(). Condition to catch fixed.
= 6.32 May 15 2024
* Fix. Integration. External forms integration refactored.
* Fix. Settings. Updated statement for import/export settings on wpms.
* Fix. Cron. Fixed updateTask function to save the last_call param.
* Fix. Common. Important requests parameters fixed.
* Fix. Settings. Added unique check for urls.
* Fix. Integrations. Added statement for compatibility with the7 theme.
* Fix. Integrations. Forbidden message appear was updated.
* Fix. EmailEncoder. Added statement to skip.
* Fix. EmailEncoder. Added exclusion for compatibility with StylishCostCalculator.
* Fix. Integrations. Added statement to exclusion for BuddyPress.
* Fix. Integrations. Added excluded statement for MemberPress.
* Fix. Integrations. Skip fluentcrm unsubscribe request.
* Fix. Integrations. Updated base integration flow.
* Fix. Pixel. Added statement to draw logic.
* Fix. Common. Getting ct_no_cookie_hidden_field data. Error handled on case of recursion level 5.
= 6.31 Apr 18 2024
* New. Integrations. Added ContactFormPlugin handler.
* Upd. Integrations. Skip new action for WordPress File Uploader.
* Upd. Settings. Advanced setting info added.
* Fix. Comments moderation. Do not auto-approve comments if license is expired.
* Fix. Code. ES Lint github action fixed.
* Fix. Code. General. Compatibility with php 8.2.
* Fix. Integration. WooCommerce. Event token added and JS status fixed.
* Fix. Integrations. Added statement for handling space in attribute name.
* Fix. Integrations. Added handler for KadenceBlocks.
* Fix. Integrations. Skip WP Fusion Abandoned Cart Addon service requests.
* Fix. Integrations. Prevented multi request after send.
* Fix. SFW update. Get only common lists on expired key.
* Fix. SFW update. Fixed case when DirectUpdate type always calls if has been called once.
* Ref. Code. Function ct_preprocess_comment refactored to integration class.
* Ref. Code. External forms. Deleted unnecessary conditions.
= 6.30 Apr 4 2024
* New. Integration. Jobstack theme register form protection implemented.
* Fix. Integration. Skip Pixelyoursite service action.
* Fix. Settings. Fixed switcher for email encode.
* Fix. Integration. Search form protection fixed.
* Fix. Integration. Adding to cart protection fixed.
* Fix. Integration. Elementor Pro. Event token gathering fixed.
* Fix. Integration. External forms protection fixed.
* Fix. Integration. Happy Forms integration fixed.
* Fix. Integration. Prevented error on Ninja forms.
* Fix. Integration. EasyDigitalDownload fixed.
* Fix. Integration. Salesforce external form fixed.
* Fix. Integrations. Catching js params on BuddyPress.
* Fix. Integrations. Fluent booking. Fix localize script.
* Fix. Code. Removed redundant parameter source
from private_list_add
handler method.
* Fix. Code. Add default key to debug call.
* Fix. Code. JS. Core.attr fixed.
* Fix. Code. Added eslint-windows npm script to run eslint on windows systems.
* Ref. ApbctSFW. Switch to direct update logic.
= 6.29.1 Mar 26 2024
Fix. Cookies. Alternative cookies set fixed.
= 6.29 Mar 14 2024
New. Integration. BookingPress integration.
New. Integration. OptimizePress integration.
Upd. Anti-Crawler. UA updating fixed.
Fix. Code. JS bundle fixed.
Fix. Bot detector JS lib. Event token field removed from GET params.
Fix. Pixel. Pixel URL getting fixed.
Fix. Email encoder. Skip Divi Builder generated content from encoding.
Fix. Integration. Goodlayers LMS plugin registration exclude from skipping.
Fix. Integration. EasyDigitalDownloads integration fixed.
Fix. Bot detector. Including bot detector wrapper script fixed.
= 6.28 Feb 28 2024
* New. Integrations. Avada Fusion form builder new implementation added.
* New. Integrations. Newsletter Tribulant eraly ajax check.
* New. Integrations. Divi Builder email opt-in subscription form.
* New. Integrations. Hubspot forms protected via div-click.
* New. Integration. Fluent Booking PRO calendar.
* Upd. Integrations. Elementor Pro. Refactored to integration class.
* Upd. Comments and user checker. Now use local datetime in the checker logs.
* Fix. Integrations. Protected request anonymous add to cart.
* Fix. Integrations. Mailpoet. Bot detector handled, message cleared.
* Fix. Integrations. Fluent forms. Bot detector handled, message cleared, visible fields array fixed, hook deprecation handled.
* Fix. Integrations. Updated ws-forms handler.
* Fix. Integrations. Submit time calculating fixed.
* Fix. WooCommerce. Added new sign of wp-ajax to skip Paystation service requests.
* Fix. WooCommerce. Skip “woo-stripe-payment” service request.
* Fix. SFW. SFW updating process fixed.
* Fix. SFW update. Do not warn user if we cannot remove index.php.
* Fix. AJAX. Skip “Paid Membership” plugin service actions.
* Fix. State. WP options. Broken serialized data handling.
* Fix. GetFieldsAny. Handle warning.
* Fix. Integration. Easy Digital Downloads. Registry during checkout handled. Service actions for discount recount skipped.
* Fix. GetFiledsAny. Try to parse URL only for single lined message.
* Fix. Div-click protection. Skipped already protected div on further call of window.load.
* Fix. Integration. WPFomrs excluded form external forms check.
= 6.27 Feb 14 2024
* New. Integrations. Added protect for outside iframe.
* New. Integrations. Classifield theme users registering protection implemented.
* Upd. General. Removed deprecated ips.
* Fix. Integrations. WpDiscuz. Duplicated request fixed. Bot detector field handling added.
* Fix. Integrations. Happy forms. NoCookie hidden field added via ajaxSetup.
* Fix. Integrations. Undefined: key \’lable\’ fixed.
* Fix. Integrations. HivePress. Service requests skipped.
* Fix. SFW. Check array key exist before use it.
* Fix. apbctPrepareBlockForAjaxForms. The method ajaxComplete() is deprecated, used on() instead.
* Fix. WooCommerce. Skip Apple Pay service request if WooCommerce check is disabled.
* Fix. WooCommerce. Added new sign of wp-ajax to skip WC order check.
* Fix. Integrations. Ninja Forms – added an exception for external forms.
= 6.26 Feb 01 2024
* New. Integration. WP GeoDirectory. Skip service actions and get necessary data directly on the hook ‘geodir_validate_ajax_save_post_data’.
* New. Integration. Kali Forms and Kali Forms pro direct integration.
* Fix. Comments. Added description.
* Fix. jQuery ajaxSetup interception. Logic refactored to fix unexpected interceptions during NoCookie data attachment.
* Fix. CleanTalk response. Fix UTF-8 decode/encode for non-mbstring instances.
* Fix. Integrations. Refactoring the definition of amp request.
* Fix. Integrations. Prevent undefined warnings occurring on WpForms.
* Fix. Integrations. Skip mailpoet service requests.
* Fix. SFW update. Direct update fixed. Queue stage status fixed.
check links
setting description fixed.aria-label
.<
div> in custom response message.
* Update. WPMS. Update counters for spam users.
* Update. SFW. Update message on sfw die page.
* Fix. Manage Spam Comments. Fixed approve comment logic.
* Fix. External forms.
* Fix. Block message for BricksExtras.
* Fix. Excluded resize-image().
* Fix. FluentForm integration.
* Fix. Excluded requests from Profile Builder.