=== AntiSpam by CleanTalk - No Captcha, no comments & registrations spam ===
Contributors: znaeff, shagimuratov, vlad-cleantalk
Tags: anti-spam, antispam, bbpress, buddypress, captcha, capcha, captha, catcha, cf7 spam, comments, contact form spam, signup, spam, spammers, spammy, woocommerce, wordpress spam, booking, order, subscription, gravity spam, jetpack, bots, contact form 7, contact form, registrations, ninja, Fast Secure Contact, Gravity forms, formidable, mailchimp, s2member, protection, protect, email, akismet, plugin, contact, recaptcha, google captcha, google recaptcha, math, security, login, blacklist, prevent spam comments, wordpress, User Frontend, bulk delete, bulk remove, cloudflare, widget, review, auth forms, firewall, ddos, cleantalk, mailpoet, profile builder, comment spam, registration spam, spam comments, comment moderation, spam bots, block spam, signup spam, spam blocker, spam filter, user registration spam,pingback,trackback, spam trackbacks, anti-spam plugin, varnish, amp, spam free,cache, cdn
Requires at least: 3.0
Tested up to: 4.5
Stable tag: 5.39.1
License: GPLv2
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Max power spam protection, all-in-one, premium anti-spam. No comments spam & registrations spam, no email spam, protects any forms. Forget spam.
== Description ==
No CAPTCHA, no questions, no counting animals, no puzzles, no math and no spam bots.
= AntiSpam features =
1. Stops spam comments.
1. Stops spam registrations.
1. Stops spam contact emails.
1. Stops spam orders.
1. Stops spam bookings.
1. Stops spam subscriptions.
1. Stops spam in widgets.
1. Check existing comments for spam.
= Public reviews =
> Using CleanTalk on WPLift was a great test as we receive huge amounts of spam.
> *Oliver Dale, WPLift.com.*
= Comments spam protection =
Supports native WordPress, JetPack comments and any other comments plugins. Plugin moves spam comments to SPAM folder or you can set options to silently ban spam comments. You can enable options in the plugin settings to auto delete comments from SPAM folder.
= Spam bots registrations filter =
Filters spam bots on registration forms WordPress, BuddyPress, bbPress, S2Member, WooCommerce, Profile builder and any other registrations plugins.
= Protection against contact form spam =
Plugin is tested and ready to protect against spam emails via Formidable forms, Contact form 7, JetPack Contact form, Fast Secure Contact form, Ninja forms, Landing pages, Gravity forms and any themes/custom contact forms.
= WooCommerce spam filter =
Anti-spam by CleanTalk filters spam registrations and spam reviews for WooCommerce. Plugin is fully compatible with WooCommerce 2.1 and higher.
= Newsletters filter =
Anti-spam by CleanTalk filters spam subscriptions for MailPoet, MailChimp, PopupAlly and many other newsletters plugins.
= Spam filter for themes contact forms =
Plugin blocks spam emails via any themes (built-in) contact forms. With AJAX forms plugin silently (without any error notices on WordPress frontend) filters spam emails.
= Other spam filters =
* WordPress Landing Pages.
* WP User Frontend.
* Any WordPress form (options for 'Custom contact forms').
* Any submission to site (options for 'Check all POST data')
= Compatible with WordPress cache plugins =
* W3 Total Cache, Quick Cache, WP Fastest Cache, Hyper Cache, WP Super cache and any other cache plugins.
= Check existing comments for spam. Bulk comment removal =
With the help of anti-spam by CleanTalk you can check existing comments to find and quickly delete spam comments at once. To use this function, go to WP Console->Comments->Find spam comments.
= Check existing users for spam. Bulk account removal =
With the help of anti-spam by CleanTalk you can check existing accounts to find and quickly delete spam users at once. For use this function, go to WP Console->Users->Check for spam.
= Low false/positive rate =
This plugin uses multiple anti-spam tests to filter spam bots with as lower false/positive rate as possible. Multiple anti-spam tests avoid false/positive blocks for real website visitors even if one of the tests fail.
= How CleanTalk improves SEO for your website? =
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.
There are different ways of improving your site's loading performance. One important parameter for site performance is to install well-developed plugins from a reputable source.
Among anti-spam plugins CleanTalk Anti-Spam is one of the fastest. Despite the large plug-in functionality, the developers have optimized the performance of the plugin so that 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
= How CleanTalk works? =
* A visitor writes a comment or registers
* CleanTalk plugin sends action parameters into the CleanTalk cloud
* Service analyzes the parameters
* If this is a visitor, the comment will be published. If it’s a spam bot, then CleanTalk blocks this comment or registration.
* Parameters are written to the log which can be viewed in the Control Panel service.
The CleanTalk team has been developing cloud-based spam protection for 5 years and has created a truly reliable anti-spam service designed for you to ensure your safety.
= Spam attacks log =
Service CleanTalk (this plugin is a client application for CleanTalk anti-spam service) records all filtered comments, registration and other spam attacks in the "Log of spam attacks" and stores the data in the log for up to 45 days. Using the log, you can ensure reliable protection of your website from spam and no false/positive filtering.
= SpamFireWall =
CleanTalk has an advanced option "SpamFireWall". This option 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 SpamFireWall significantly reduces the load on your web server.
SpamFireWall also makes CleanTalk the two-step protection from spam bots.
SpamFireWall 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.
= How SpamFireWall works? =
* The visitor enters to your web site.
* HTTP request data is checked against the nearly 5.8 million identified IP spam bots.
* If it is an active spam bot, the bot gets a blank page, if it is a visitor then they receive the site page. This is completely transparent to the visitors.
All the CleanTalk SpamFireWall activity is being logged in the process of filtering.
= SpamFireWall DDoS Protection (Experimentally option) =
SpamFireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, SpamFireWall blocks all requests from bad IP addresses. Your website gives the intruder a special page with description of DDoS rejection instead of the website pages. Therefore SpamFireWall can help to reduce CPU usage on your server.
= XML-RPC brute force protection =
SpamFireWall can mitigate XML-RPC brute force attacks. It blocks XML-RPC attacks from bad IP addresses. This helps to prevent bruteforce attacks by a Remote Procedure Call.
= No spam comments, no spam registrations, no spam contact emails, no spam trackbacks. CAPTCHA-less anti-spam for WordPress =
Spam is one of the most irritating elements. Rates for spam increases every year and conventional anti-spam can no longer handle all the spam bots. CleanTalk prevents and automatically blocks spam. You'll be surprised how effective CleanTalk is in protecting against spam.
= AntiSpam plugin info =
CleanTalk is an all-in-one anti-spam solution for WordPress that protects login, comments, contact and WooCommerce forms at once. You don't need to install separate anti-spam plugins for each form. This allows your blog to work faster and save resources. After installation you will forget about spam; your CleanTalk plugin will do all the work. You won't have to deal with spam as CleanTalk does this for you automatically.
CleanTalk is a transparent anti-spam tool, we provide detailed statistics of all entering comments and logins. You can always be sure that **there are no errors**. We have developed a mobile app for you to see anti-spam statistics wherever.
We have developed anti-spam for WordPress that provides maximum protection from spam bots, 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 methods that inconvenience the communication (CAPTCHA, question-answer etc.), and offers your site visitors a more convenient one.
CleanTalk is a premium anti-spam service for WordPress and the plugin works with our cloud anti-spam CleanTalk Service. CleanTalk offers a free trial and 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 providing anti-spam protection. Paying for a year of anti-spam service, you save a lot more and receive:
* Up to 99.998% protection against spam bots.
* Time and resources saving.
* More registrations/comments/visitors.
* Protect several websites at once at different CMS.
* Easy to install and use.
* Traffic acquisition and user loyalty.
* 24/7 technical support.
* Clear statistics.
* No captcha (reCaptcha), puzzles, etc.
* Free mobile app to control anti-spam function at your website.
= Additional features =
* Online, daily and weekly anti-spam reports traffic VS spam.
* Apps for iPhone, Android to control anti-spam service, comments, signups, contacts, with traffic and spam statistics for last 7 days.
* AntiSpam apps for most popular CMS on cleantalk.org.
= How to protect sites from spam bots without CAPTCHA? =
The most popular method is CAPTCHA - the annoying picture with curved and sloping symbols, which are presented to the visitor to decipher and fill in. It 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 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.
*Why are they spamming me?*
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.
= CleanTalk's features =
CleanTalk is one of the fastest plugins that allows you to lower the server load. One of the important parameters for each web master is the speed of the site, so we make sure that our plugin consumes as little as possible of server resources. Cloud service provides the advantage that all the checks take place in the cloud.
CleanTalk has developed unique algorithms to assess visitor behavior. CleanTalk analyzes user behavior and parameters of completed forms. Our anti-spam module, installed on your website, sends the behavior parameters of either a visitor or spam bot. These parameters are estimated, and the CleanTalk service makes a decision – to post a message or to define it as spam and reject. On the basis of such checks, the service forms its own list of email addresses used by spam bots.
The registrations of visitors are checked in a similar manner. The service adds not only email addresses to the blacklist, but also IP addresses and domains of websites that are promoted through spam mailout. All of this happens automatically and requires no action from the administration of the website. At 2.5 million queries the service makes a mistake in 40-45 cases, i.e. CleanTalk detects spam with 99.9982% accuracy. We constantly monitor these errors and make adjustments to our algorithms, Even with this exceptional accuracy our team is aiming to improve figures over time.
All-in-one. CleanTalk immediately protects all forms – comments, registration, feedback, contacts. No need to install additional plugins for each form. You save resources and increase performance of your website.
Spam attacks log. Service CleanTalk records all filtered comments, registration and other spam attacks in the “Log of spam attacks” and stores the data in the log for up to 45 days. Using the log, you can ensure reliable protection of your website from spam and experience no false/positive filtering.
With the help of anti-spam by CleanTalk you can check existing comments and users, to find and quickly delete spam comments at once. This allows administrators of websites to automatically check and identify spam bots, comments and users, which were not detected by conventional anti-spam tools. Checking existing comments and users is made against a database of the nearly 2 million certain spam bots. Detailed statistic allows CleanTalk customers to control the whole process.
CleanTalk has an advanced option “SpamFireWall”. This option allows you to block the most active spam bots before they get access to your website. It prevents website pages loading when attempted by by spam bots, so your web server doesn’t perform unnecessary scripts on these pages. Also it prevents scanning of website pages by spam bots. Subsequently SpamFireWall significantly reduces the load on your web server. SpamFireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, SpamFireWall will block requests from bad IP addresses. Your website gives the intruder a special page with a description of DDoS rejection instead of the website pages. SpamFireWall can help to reduce of CPU usage on your server for this reason.
“CleanTalk team has been developing a cloud spam protection system for five years and has created a truly reliable anti-spam service designed for you to guarantee your safety”.
= We recommend =
Audience engagement plugin Feedweb
> Max power, all-in-one, premium anti-spam WordPress plugin. No comments & registrations spam, no contact spam, protects any forms. Just install and forget spam.
== Installation ==
= Setup anti spam plugin =
1. Download, install and activate Anti-spam by CleanTalk.
1. Get Access key https://cleantalk.org/register
1. Enter Access key in the settings,
> WordPress console -> Settings -> CleanTalk
1. Do dummy spam comment (registration or contact message) with email **stop_email@example.com**. You should see notice,
> *** Forbidden. Sender blacklisted. ***
**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.
Done! The plugin is ready to use.
= How can setup plugin in WPMU version? =
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 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.
= Manage and control spam protection =
Go to Dashboard at the cleantalk.org or use Android, iPhone anti-spam app to manage and control spam protection.
== Frequently Asked Questions ==
= Does the plugin protects against brute force, DoS attacks as well as against spam attacks? =
No, it doesn't. Anti-spam by CleanTalk **is only anti-spam solution** for comments, registrations and other other forms on a website. Plugin saves your time against manage spam problem, but doesn't protect against any security issues.
= Does anti spam protection safe for mobile visitors? =
Yes, it does. Plugin doesn't block mobile visitors as well as desktop websites visitors. Because this plugin uses several anti-spam tests to detect spam bots and lower false/positive rate. Multiple anti-spam tests helps avoid false/positive blocks for real website visitors even if one of tests failed.
= How does the plugin work with spam comments? =
Spam comments moves to SPAM folder or you can set option to silent ban spam comments.
= How does the plugin stop spam? =
Plugin uses several simple tests to stop spammers.
1. JavaScript anti-spam test. 99% spam bots doesn't have all JavaScript functions support. So, the plugin has code which can run normal visitor and can't run the spam bot.
1. Checks by Email, IP, domains at spam activities list. The plugin online use spam activity database at cleantalk.org, which are consist more then 1 billion records about spam activity IPs, Email, Domains and ASN. If the senders IP or Email matches with database, the sender gets some spam scores. To reduce false/positive rate the plugin doesn't use only blacklist test to ban spammers. The sender will be banned only if multiple spam test failed.
1. Comment submit time. Spam bots usually send post immediately after page load, because spam bots not really fill the web form, they are only send $_POST data to the blog. The normal visitor sends the data within several seconds or minutes.
= Will anti-spam protects my theme? =
Yes, it will. The Anti-spam by CleanTalk compatible with any WordPress themes.
= How can I test anti-spam protection? =
Please use email **stop_email@example.com** for comments, contacts or signups to see how the anti-spam protection works. Also you can see logs for last 7 days at Control panel or look at folder "Spam" for banned comments.
= Is the plugin effective against spam bots? =
Plugin Anti-spam by CleanTalk stops up to 99.998% of spam comments, spam signups (registrations), spam contact emails, spam subscriptions, spam bookings or spam orders.
= What about pingback, trackback spam? =
Plugin by default pass pingbacks without any checks. All trackbacks will be blocked if the sender had spam activity.
= Can I use CleanTalk with Akismet? =
Sure, you can use CleanTalk with Akismet. In this case probably you will have bigger false/positive rate (when legitimate comments/signups denies), but you will have stronger antispam protection at website.
= Is CleanTalk better than Akismet? =
Please look features comparison here https://cleantalk.org/cleantalk-vs-akismet
= Can I use CleanTalk to remove pending spam comments? =
Yes, you can. The plugin has option to test all pending comments via database of spam active IP/Email, finded spam comments plugin moves to Trash folder.
= How the plugin finds spam in pending comments or registered accounts? =
Plugin checks all not spam comments against blacklists database and show you senders that have spam activity on other websites.
There is some differencies between blacklists database and API to protect against spam bots registrations/comments online. Blacklists show all history of spam activity, but our API (that used in spam tests) used another parameters, too: last day of activity, number of spam attacks during last days etc. This mechanisms help us to reduce number of false positivitie. So, there is nothing strange, if some emails/IPs will be not found by bulk comments/accounts test.
To check comments please click this,
> WordPress console -> Comments -> Find spam comments
To check users please click this,
> WordPress console -> Users -> Find spam users
= Should I use another anti-spam tools (Captcha, reCaptcha and etc.)? =
CleanTalk stops up to 99.998% of spam bots, so you can disable other anti-spam plugins (especially CAPTCHA like anti-spam plugins). In some cases several anti-spam plugins can conflict, so it will be better use just one plugin.
= Is the plugin WordPress MultiUser (WPMU or WordPress network) compatible? =
The plugin is WordPress MultiUser (WPMU or WordPress network) compatible. Each blog in multisite environment has individual anti-spam options for spam bots protection.
= After installation I noticed in the statistics that the number of spam attacks increased =
There are a few reasons for this:
* With the indexing of your web-site by the search systems, appearance of external links and better search results position, your web-site attracts more and more spambots.
* Non-transparent protection systems like CAPTCHA or question/answer, that don't have spam attacks statistics, don't let you see the whole picture, or the picture is incomplete.
* Counting methods for spam attacks and spam bots are different for different systems, which explains the diversity. We seek to provide detailed statistics.
= Why my dummy "spam" comment passed to the WordPress? =
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, becuase the plugin detect sender as a human. So, use special email *stop_email@example.com* to test anti-spam or wait a few days to see how the plugin works.
= Is it free or paid? =
The plugin is free. But the plugin uses CleanTalk cloud service to filter spam bots. You have to register an account and you have free trial to test anti-spam for comments, registrations, bookings, contacts or orders. When the trial (on CleanTalk account) is finished, you can renew the subscription for 1 year or deactivate anti-spam plugin.
= Can I use CleanTalk with cache plugins? =
Anti-spam by CleanTalk doesn't use static HTML code into templates, so all anti-spam functions works correctly with any WordPress cache plugins.
= Does the plugin protects against spam bots at forms with third-party services? =
Yes, it does. Plugin protects web-forms on your websites which are send data to third-party servers (like MailChimp). To enable this protection set option 'Protect external forms' in plugin settings.
= Does CleanTalk compatible with Cloudflare? =
CleanTalk is fully compatible with CloudFlare. Service doesn't filter CloudFlares IP's (AS13335) over blacklists database, so in this way plugin/service filters spam bots uses other anti spam tests.
= Does CleanTalk compatible with a content delivery network (CDN)? =
Yes, it does. CleanTalk works with any CDN system, i.e. CloudFlare, MaxCDN, Akamai.
= Can I use CleanTalk functionality in my plugins? =
Yes, you can. Just use following snippet:
Settings -> CleanTalk -> Advanced settings
In that way plugin will protect WordPress comments, registrations and most of popular contact forms, but will not protect some of rarely used contact forms.
= Does the anti-spam plugin work with Accelerated Mobile Pages (AMP)? =
Yes, it does. But you have to turn off the option 'Use AJAX for JavaScript check' in Advanced settigns to be fully compatible with Accelerated Mobile Pages.
== Other notes ==
= Troubleshooting Guide =
Anti-spam by CleanTalk support forum | Plugin FAQ
You can contact to technical support for any questions at any time. If you have questions or suggestions, we will be happy to help you. Please note that we accept requests in English only.
Technical Support 24/7 to help you get accustomed to the work of the anti-spam service.
If you have specific needs, you can contact our Cleantalk customer support team at any time, day or night.
We strive to answer all emails within 1-2 hours, and most are answered in substantially less time.
When you contact CleanTalk technical support, we recommend to give us following:
1. Site URL.
1. CMS name and version.
1. URL of page with the comments / registration / feedback form.
This will help us give you a faster response. Please write us here https://cleantalk.org/my/support.
If you're having trouble getting things to work after installing the plugin, here are a few things to check:
1. If you haven't yet, please upgrade plugin to the latest version.
1. If you have error '*** Forbidden. Enable JavaScript. Anti-spam service cleantalk.org. ***' please check JavaScript support in your browser and do JavaScript test at this page Check out JavaScript support.
1. If you have spam comments, signups or contacts please check the Access key at plugin settings. The key should be same as you can find in service Dashboard.
= Spam protection, backend and frontend perfomance =
We develop plugin to do it as optimized as possible, CleanTalk doesn't downgrade response time in backend or frontend. The plugin proccess only POST requests to WordPress core, it tackes less than 1 second to return results. Here are some P3 Profiler results from a real WordPress blog,
> WordPress Plugin Profile Report
> ===========================================
> Report date: July 9, 2015
> Theme name: amongsthumans (Canvas child theme)
> Pages browsed: 24
> Avg. load time: 2.1155 sec
> Number of plugins: 28
> Plugin impact: 45.25% of load time
> Avg. plugin time: 0.9573 sec
> Avg. core time: 0.1093 sec
> Avg. theme time: 0.9339 sec
> Avg. mem usage: 44.94 MB
> Avg. ticks: 9,890
> Avg. db queries : 65.00
> Margin of error : 0.1149 sec
> Plugin list:
> ===========================================
> P3 (Plugin Performance Profiler) - 0.1290 sec - 13.48%
> Advanced Code Editor - 0.0045 sec - 0.47%
> Bulk Comment Remove - 0.0029 sec - 0.30%
> Bulk Delete - 0.0275 sec - 2.87%
> Cleantalk Spam Protect - 0.0187 sec - 1.95%
> Custom Share Buttons with Floating Sidebar - 0.0173 sec - 1.81%
> Exclude Pages - 0.0009 sec - 0.10%
> Google Sitemap Generator - 0.0032 sec - 0.34%
> Jetpack by WordPress.com - 0.3644 sec - 38.06%
> Last Modified Timestamp - 0.0031 sec - 0.32%
> Le Petite Url - 0.0112 sec - 1.17%
> Onenote Publisher - 0.0015 sec - 0.16%
> Popups Premium Plugin - 0.0074 sec - 0.77%
> Popups - WordPress Popup - 0.0419 sec - 4.37%
> Post Duplicator - 0.0059 sec - 0.62%
> Post Teaser - 0.0237 sec - 2.48%
> Q2W3 Fixed Widget - 0.0017 sec - 0.18%
> SSL Insecure Content Fixer - 0.0111 sec - 1.16%
> TinyMCE Advanced - 0.0022 sec - 0.22%
> Ultimate Follow Me Plugin by Free Blog Factory - 0.0008 sec - 0.08%
> WooThemes Helper - 0.0282 sec - 2.95%
> Wp Social Avatar - 0.0013 sec - 0.13%
> WP User Avatar - 0.0559 sec - 5.84%
> Wpcommentcleaner - 0.0119 sec - 1.24%
> Wpdiscuz - 0.0369 sec - 3.85%
> Online Backup for WordPress - 0.0039 sec - 0.41%
> WPSSO Pro Update Manager (WPSSO UM) - 0.0114 sec - 1.19%
> WordPress Social Sharing Optimization (WPSSO) Pro - 0.1288 sec - 13.45%
= Translations =
* Danish (da_DK)
* French (fr_FR) - thanks to Gilles Santacreu http://net-ik.net
* German (de_DE)
* Italian (it_IT)
* Polish (pl_PL)
* Portuguese (pt_PT)
* Spanish (es_ES) - thanks to Andrew Kurtis and WebHostingHub
* Russian (ru_RU)
= Requirements =
WordPress 3.0 at least. PHP 5 with CURL or file_get_contents() function and enabled 'allow_url_fopen' setting. Sign up to get an Access key.
== Screenshots ==
1. AntiSpam settings.
1. AntiSpam stopped spam bot at the CAPTCHA less registration form. The plugin provide explanation to visitor and websites about eache rejected comment/registration or contact message.
1. Use AntiSpam analytics tool for each website in service Dashboard to have information about spam/legitimate statistics.
1. Use AntiSpam log to control anti-spam plugin.
1. CleanTalk works faster than most of other anti-spam plugins.
== Changelog ==
= 5.39.1 2016-04-04 =
* Improved AJAX based anti-spam test with HTTPS backends.
* Added fix to avoid issue with empty ct_info_flag on JavaScript side.
* Added logic to exclude caching for SpamFireWall.
* Removed a condition to skip accounts with 127.0.0.1 IP in spam test for registered acconts.
= 5.38.1 2016-03-24 =
* Fixed issue with PHP sessions and 'The session id is too long or contains illegal characters'.
* Removed SpamFireWall protection on /feed page.
* Disabled anti-spam tests for AJAX calls if the option 'Custom contact forms' is turned off.
* Added reject notice for spam submissions on Gravity forms with AJAX calls.
= 5.37.3 2016-03-10 =
* Fixed bug with broken MailPoet previews.
* Fixed bug with broken Geo My WP pop-up windows.
* Fixed issue with mb_convert_encoding() function.
* Removed double JavaScript code in front-end.
* Removed unused variables in anti spam logic.
* Added option 'Set cookies' (turned on by default). If the option turned off, the plugin will not generate cookies, but in this case plugin will not protect some rarely used contact forms. Any way, turn this option off be compatible with Varnish in spam protection for WordPress core comments, registrations and most popular contact forms.
* Added anti-spam protection for Gravity forms via option 'Contact forms' with hook gform_entry_is_spam().
= 5.36.1 2016-02-05 =
* Fixed bug, when users receive error after logging in
* Improve anti-spam filters for contact forms.
= 5.36 2016-02-04 =
* Improved JavaScript anti spam protection
* Improvements for avoiding blocking requests from payment systems
= 5.35 2016-01-14 =
* Added support for IP licensing
* Some anti-spam protection improvements
* Small backend interface fixes
= 5.34.1 2015-12-17 =
* Fixed trackback antispam protection: improved checking mechanism
* Fixed problem with blocking MailPoet: added exclusions in spam checking algorithm
= 5.34 2015-12-10 =
* Improved spam checking mechanism
* Added "Collect browser details" option for better antispam protection
* Fixed custom contact forms checking for AJAX requests
* Minor translations fixes
= 5.33.1 2015-12-04 =
* Fixed issue with BBPress: restored old user permission checking mechanism
* Fixed anti-spam comments checking: sometimes get_comments returned wrong comments number
* Fixed bulk checking: made numeric indexes in users and comments arrays
* Fixed trackback and pingback checking: removed exception for checking
= 5.33 2015-12-01 =
* Backend interface fixes
* Improved SpamFireWall efficiency
* Improved performance of anti spam checking
= 5.32 2015-11-26 =
* Added improvements for manual spam detection
* Fixed errors in backend
* Fixed bulk users anti spam checking
* Added indicator for bulk spam checking
* Added "Get access key automatically" button
= 5.31 2015-11-11 =
* Improved backend performance
* Fixed counter of approved/blocked spam attacks
* Fixed SpamFireWall logging
= 5.30 2015-11-05 =
* Improved anti-spam checking
* Optimized performance
* Fixed blocking email preview in MailPoet
* Interface fixes
* WPMU interface fixes
= 5.29 2015-10-27 =
* Optimized performance
* Fixed bugs in custom contact forms spam checking
= 5.28.7 2015-10-23 =
* Optimized PHP sessions creation algorithm. This fix should increase plugin perfomance on hostings without retenion of PHP sessions files.
* Removed autoredirection to plugin settings after plugin activation.
= 5.28 2015-10-16 =
* Fixed errors in anti-spam checking
* Restored options for spam checking registrations and cpmmon contact forms
* Improved spam protection
* Fixed problems with AJAX functionality in MailPoet, WooCommerce and other AJAX plugins
= 5.27 2015-10-13 =
* Improvements in SpamFireWall feature
* Code optimization
* Backend interface fixes
= 5.26 2015-10-05 =
* Added WordPress Language Pack support
* Removed spam checking for some autorisation plugins
* New experimental feature: SpamFireWall
= 5.25.2 2015-09-28 =
* Fixed backend bug
= 5.25.1 2015-09-28 =
* Added widget with anti-spam statistics
* Added information about blocked spam attacks in admin dashboard and CleanTalk settings
* Added ability not to check comments for users with 3 or above allowed comments
* Added an option 'Help others known CleanTalk' to show information for site visitors, that your site is protected from spam by us
* Some backend interface settings
= 5.24.1 2015-09-16 =
* Fixed some errors in frontend
* Fixed access key saving
= 5.24 2015-09-14 =
* Backend interface fixes
* Improvement for AJAX JavaScript spam checking
= 5.23 2015-09-01 =
* Fixed BuddyPress profile search false positivities of anti-spam protection.
* Some interface fixes of bulk users & comments spam checking
= 5.22 2015-08-26 =
* Fixed possible XSS issue for anti-spam test on third-party forms.
= 5.21 2015-08-21 =
* Fixed bug with skipping spam submissions
* Fixed bug with receiving old user_token for viewing anti-spam statistics
* Small backend fixes
= 5.20 2015-08-15 =
* Fixed anti-spam stats in admin bar - now statistics updates every hour
* Fixed issue with skipping spam submissions
* Added some PHP-constants for advanced users - CLEANTALK_AJAX_USE_BUFFER and CLEANTALK_AJAX_USE_FOOTER_HEADER can be defined to true or false in wp-config.php to control method, which will be used for injection of AJAX script.
= 5.19 2015-08-11 =
* New feature: anti-spam checking for registered users
* Fixed issue with AJAX JavaScript anti-spam test.
* Fixed issue with SEO Yoast xml sitemaps and JavaScript anti-spam test.
= 5.18 2015-08-04 =
* Fixed issue with user_token
* Added anti-spam API, see our FAQ
= 5.17 2015-07-23 =
* Fixed infinite redirection after activation
* Minor backend fixes
= 5.16 2015-07-22 =
* Fixed external services checking
* Fixed mass comments deletion
* Fixed AJAX anti-spam protection
= 5.15 2015-07-16 =
* New feature: anti-spam protection for forms, that uses external services
= 5.14 2015-07-03 =
* Added anti-spam protection for some themes and plugins
* Some backend fixes
= 5.13 2015-06-12 =
* Closing notification for anti-spam renew
* Fixed bulk anti spam comment checking
= 5.12 2015-06-01 =
* Added option for checking all post data for spam
* Some JavaScript protection improvements
* Added option for old JavaScript check (without AJAX)
= 5.10 2015-05-25 =
* Fixed Javascript error on some forms
= 5.9 2015-05-21 =
* Fixed Javascript error on CF7 and JetPack
* Some backend and frontent fixes
= 5.8 2015-05-18 =
* Minor fixes
= 5.7 2015-05-18 =
* Fixed French translation
* Fixed protection algorithm
= 5.6 2015-05-11 =
* Fixed translation
* Fixed bulk comments anti-spam checking
* Added option for disabling anti spam statistics in adminbar
* Some security fixes
= 5.5 2015-04-29 =
* Fixed security issue
* Some interface fixes
= 5.4 2015-04-27 =
* Some interface and functionality changes in plugin settings page
* Added counter for anti-spam statistics in admin bar
= 5.3 2015-04-13 =
* Added anti-spam protection for Divi theme contact forms
* Added anti-spam protection for MyMail contact forms
* Added anti-spam protection for MailPoet Newsletters
* Some interface and functionality changes in backend
= 5.2 2015-04-01 =
* Added link for anti-spam statistics
* Added WP User Frontend Pro registration form protection
= 5.1 2015-03-24 =
* Fixed site crash after installing 5.0 on some websites
= 5.0 2015-03-24 =
* Added bulk comments checking for spam via CleanTalk blacklists
* Added anti-spam form protection for 'Ajax Login & Register'
* Fixed JetPack form protection
= 4.24 2015-03-20 =
* Added immediate spam protection activation.
= 4.22 2015-03-17 =
* Added button for automatic spam protection key getting.
= 4.21 2015-03-11 =
* Added license renew notification.
= 4.20 2015-03-03 =
* Added German, Italian, Polish, Portuguese translations.
* Minor code fixes.
= 4.19 2015-02-24 =
* Increased keys lifetime for JS spam test.
= 4.18 2015-02-17 =
* Fixed bug with comments approvement - moved ct_unmark_red() to cleantalk-admin.php
* Added PayPal 'payment_status' in skip list.
* Added Akismet 'spam' status processing.
= 4.17 2015-02-12 =
* New base class.
* Divided code to 3 separate files - common, public and admin.
= 4.16 2015-02-05 =
* New base class.
* Fixed JetPack spam filters logics.
* Optimized Formidable, bbPress, BuddyPress spam filters.
= 4.15 2015-01-29 =
* Support spam test for Contact Form 7 versions before 3.0.0.
* Fixed global JS-vars for JS spam test.
* Fixed online notice cookie logics.
* Optimized spam filters for FSCF, WooCommerce, JetPack.
* Optimized option getting.
= 4.14 2015-01-19 =
* Removed deprecated option from comment approvement code.
* New API key URL.
* Trimmed API key in admin panel.
* Added current options to array sended to CleanTalk servers.
= 4.13 2014-12-29 =
* Fixed bug with autimatically aprovement not spam comments. Now this option disabled and do not override local WordPress policy.
= 4.12 2014-12-29 =
* Fixed bug with 'Wrong Access key...' notice in WordPress dashboard.
* Fixed filtration bug in WordPress dashboard login form.
= 4.11 2014-12-22 =
* Improved anti-spam protection for custom contact/registration/subscribe forms.
* Improved anti-spam protection for comments.
* Accelerated plugin speed for comments, regirstrations and contacts.
* Added translation to French.
= 4.10 2014-12-10 =
* Improved anti-spam protection for custom contact/registration/subscribe forms.
* Option 'Custom contact forms' enabled by default for new setups.
* Removed settings "Publish relevant comments", "Use encrypted (SSL) connection".
* Added translation to Danish (thank you for Mikkel at KreativJul.dk).
= 4.9 2014-11-24 =
* Fixed spam test for Contact Form 7.
= 4.8 2014-11-19 =
* Improved anti-spam protection for BuddyPress registrations and custom contact forms.
= 4.7 2014-11-16 =
* Fixed JavaScript spam test for FastSecure contact form.
= 4.6 2014-11-11 =
* Improved anti-spam protection on BuddyPress registrations.
* Improved anti-spam protection on contact forms.
* Removed plugin sign from pending, spam comments. To get details about a comment please use Dashboard at cleantalk.org.
* Improved Access key validation function.
* Added protection for bbPress comments via stop list. Stop list function is a list to reject comments by prefiled words. To fill the list please use Dashboard at cleantalk.org.
= 4.5 2014-11-04 =
* Fixed CF7 JavaScript bug.
* Fixed rejects in bbPress guests comments.
= 4.4 2014-10-29 =
* Improved anti-spam JS test for CF7.
* Fixed 'noscript' text in FaceBook Like preview in Valenti theme.
= 4.2 2014-10-20 =
* Fixed double checks issue for BuddyPress registrations.
* Increased timeout limits to find the work server.
= 4.1 2014-10-13 =
* Optimized code for manual moderation feedback sending.
* Optimized anti-spam algorithms for comments, contacts and signups.
= 4.0 2014-10-06 =
* Improved anti-spam protection for custom contact forms.
* Improved anti-spam protection for registration forms.
= 3.9 2014-10-01 =
* Did exception to do not break to create new user in WordPress backend.
= 3.8 2014-09-19 =
* Fixed json_encode() + malformed characters.
* Fixed JavaScript issue with wpautop().
= 3.6 2014-09-15 =
* Fixed preg_match() issue for Formidable forms and Custom contact forms.
* Improved anti-spam protection for Custom contact forms.
= 3.4 2014-09-04 =
* We've added anti-spam for themes contact forms and any untested contact forms plugins. To use this test enable option "Custom contact forms" in plugin settings.
* We've added auto rotation for spam comments. Now the plugin removes comments in SPAM folder older then 15 days. This option is enabled by default.
= 3.2 2014-08-27 =
* Fixed submit_time() logic for failed submits (comments/registrations). Now form fill time resets after every failed submit.
= 3.1 2014-08-19 =
* Added anti-spam test over senders Cookies.
* Improved form fill anti-spam test.
* Improved speed selection of the nearest server to website.
* Improved anti-spam speed for comments.
* Relevance anti-spam test disabled by default. To enable test should be used option 'relevance_test'.
= 2.58 2014-08-06 =
* Added anti-spam protection for signups posted via WooCommerce order form.
* Improved anti-spam protection for Contact Form 7.
* Improved anti-spam protection for registrations. Now the plugin looking for JavaScript anti spam test results not only in POST array, but in COOKIES array too. This improvement allows protect signup forms for any untested signups plugins and themes.
* Updated PHP API. Now the plugin can resolve sender IP for websites behind proxy servers. If the proxy servers uses private IP address.
= 2.57 2014-07-29 =
* Improved anti-spam protection for comments. The plugin now proccessing website url in the comments form.
* Fixed sign remove logic for approved comments. Previous version doesn't cut sign for comments approved via AJAX call in WordPress backend.
* Fixed switching to SSL for comments. Previous version doesn't use secured connection for comments.
= 2.56 2014-07-21 =
* Fixed account status check logic. Previous version makes unnecessary test API calls when the plugin asks account status check.
= 2.55 2014-07-11 =
* Fixed bug with account status function. In backend the plugin showed notice 'Please don’t forget to disable CAPTCHA if you have it!' on every page.
= 2.54 2014-07-11 =
* Fixed signup anti-spam protection logic for BuddyPress registrations.
* Fixed anti-spam protection for JetPack contact form.
* Changed account status check logic.
= 2.53 2014-06-27 =
* Fixed anit-spam protection bug for signups.
* Changed anti-spam functions (comments and signups) priority.
= 2.52 2014-06-25 =
* Fixed 'Fatal error: Call to a member function get_error_code()' issue with signups via BuddyPress.
= 2.51 2014-06-23 =
* Added spam protection for registrations via plugin New User Approve by Josh Harrison. If the CleanTalk matched signup as spam this signup will be denied to placing in pending queue.
* Added option "Use secure (SSL) connection to CleanTalk cloud". If the option enabled plugin will communicate with CleanTalk severs via 128bit encrypted data channel. So, if you have SSL protected webforms on website you can use this option to be sure that visitors personal data safely transmits to CleanTalk servers.
* Fixed minor bug with loading backend functions.
= 2.49 2014-06-10 =
* Added spam protection for S2Member Auth.net forms.
* Added spam protection for multisite signup form.
* Optimized account status check function.
= 2.46 2014-05-19 =
* Added: HTML notice about the need to enable JavaScript.
* Fixed: Fixed pingbacks anti-spam test.
= 2.44 2014-05-12 =
* Added: Anti-spam protection for S2Member framework.
* Improved: JavaScript anti-spam test.
* Improved: Plugin load time for backend and frontend.
* Fixed: PHP warning mb_convert_encoding()
= 2.42 2014-04-29 =
* Fixed: JavaScript anti-spam test for comments.
= 2.40 2014-04-25 =
* New: Fast Secure Contact form support.
* New: WordPress Landing Pages support
= 2.38 2014-03-27 =
* Fixed: Registraion form submit time spam test.
= 2.36 2014-03-12 =
* Reversed to patches from old revisions.
= 2.35 2014-03-12 =
* New: Notifications about disabled account
* New: Improved JavaScript spam test.
* Fixed: Code optimization
* Fixed: JavaScript test for signups.
= 2.33 2014-02-12 =
* Fixed: CURLOPT_FOLLOWLOCATION bug at admin notice
= 2.32 2014-02-04 =
* New: Added notice about automatically approved comment. The notice shows only for first approved comment and only for new commentators (without approved comments) of the blog.
* New: At WordPress console added banner for notices.
* Changed: Screenshots updated.
= 2.31 2014-01-24 =
* New: Added spam protection for JetPack comments
* Fixed: cURL connection issue "Expect: 100-continue"
= 2.30 2014-01-13 =
* Changed: Improved servers connection logic.
* Fixed: Antispam test for Fomidable forms.
= 2.28 2013-12-19 =
* New: Added protection against spam bots for WooCommerce review form.
* Fixed: JavaScript anti-spam logic for WooCommerce review form.
= 2.27 2013-12-06 =
* New: Added protection against spam bots for JetPack Contact form.
* Fixed: JavaScript anti-spam logic for registrations and Contact form 7.
= 2.25 2013-11-27 =
* New: Added protection against spam bots for BuddyPress registrations.
* New: Added protection against spam bots for Contact form 7.
* New: Added Spanish (es_ES) translation.
= 2.23 2013-11-20 =
* New: Added automatic training blacklists on spam bot account deletion.
* New: Added URL to project homepage at plugin options.
* Changed: Improved anti-spam logic.
= 2.21 2013-11-13 =
* Changed: WordPress blacklists settings get priority over plugin's anti-spam settings
* Changed: Disabled management approval comments for regular commentators of the blog. Automatically approved for publication only the comments of the new blog authors.
* Changed: Removed form submit time test. Imporved JavaScript spam test.
* Changed: PHP code optimizations
= 2.19 2013-11-08 =
* New: Antispam protection from spam bots at the registration form
* Changed: Russian localization for admin panel
* Changed: PHP code optimizations
= 2.5.18 2013-11-01 =
* Fixed: Bug with selection of the last comments for post
* New: Antispam protection for Formiadble feedback forms
* New: Automatic deletion of outdated spam comments
* New: On/Off option for comments spam filtration
* Tested with WordPress 3.7.1
= 2.4.15 2013-09-26 =
* Fixed: Bug with mass comments deletion
* Changed: Russian localization for admin panel
* Tested with mulitsite setup (WordPress network or WPMU)
= 2.4.14 2013-08-29 =
* Changed: Removed feedback requests to the servers for banned (spam) comments.
= 2.4.13 2013-08-19 =
* Changed: Switched HTTP requests from file_get_contents() to CURL. Added file_get_contens() as backup connection to the servers.
* Changed: Removed feedback requests for comments moved to trash.
* Fixed: "Fail connect to servers..." error on hostings with disabled 'allow_url_fopen' PHP option.
= 2.4.12 2013-08-12 =
* Removed RPC::XML library from plugin.
* Switched plugin to HTTP+JSON connection with servers.
* Fixed bug with comments anti-spam tests with non UTF8 codepage.
= 2.4.11 2013-08-02 =
* Removed spam tests for self-made pingbacks
* Tested up to WP 3.6
= 2.4.10 2013-07-24 =
* Fixed warning in PHP 5.4
* Fixed bug with disabling comments test for Administrators, Authors and Editors
* "Stop words" settings moved to Control panel of the service
* "Response language" settings moved Control panel of the service
= 2.4.9 =
* Fixed extra debugging in base class
= 2.4.8 =
* Enabled convertion to UTF8 for comment and example text
* Optimized PHP code
= 2.3.8 =
* Enabled selection the fastest server in the pool
* Fixed work server in plugin's config
= 2.2.3 =
* Secured md5 string for JavaScript test
* Added requests's timestamp to calculate request work time
* Update base CleanTalk's PHP class
= 2.1.2 =
* Improved perfomance for processing large comments (over 32kb size)
* Improved perfomance for bulk operations with comments in Comments panel
* Added feedback request with URL to approved comment
= 2.0.2 =
* Fixed bug with JavaScript test and WordPress cache plugins
= 2.0.1 =
* Added option "Publicate relevant comments" to plugin's options.
* Added descriptions to plugin options
= 1.5.4 =
* Fixed HTTP_REFERER transmission to the servers
* Improved JavaScript spam test
* Optimized PHP code
= 1.4.4 =
* Pingback, trackback comments has moved to manual moderataion
* Added transmission to the serves comment type and URL
* Post title, body and comments separated into individual data elements
* Added priority for matched words in the comment with post title
* Enabled stop words filtration as default option
= 1.3.4 =
* Removed PHP debugging.
= 1.3.3 =
* Added notice at admin panel about empty Access key in plugin settings
* Removed HTTP link to the site project from post page
* Removed unused options from settings page
* Tested up to WordPress 3.5
= 1.2.3 =
* Fixed bug with session_start.
= 1.2.2 =
* Plugin rename to CleanTalk. Spam prevent plugin
* Integration Base Class version 0.7
* Added fast submit check
* Added check website in form
* Added feedbacks for change comment status (Not spam, unapprove)
* Added function move comment in spam folder if CleanTalk say is spam
* Disable checking for user groups Administrator, Author, Editor
* Marked red color bad words
= 1.1.2 =
* Addition: Title of the post attached to the example text in auto publication tool.
* Tested with WordPress 3.4.1.
= 1.1.1 =
* HTTP_REFERER bug fixed
= 1.1.1 =
* Added user locale support, tested up to WP 3.4
= 1.1.0 =
* First version
== Upgrade Notice ==
= 5.39.1 2016-04-04 =
* Improved AJAX based anti-spam test with HTTPS backends.
* Added fix to avoid issue with empty ct_info_flag on JavaScript side.
* Added logic to exclude caching for SpamFireWall.
* Removed a condition to skip accounts with 127.0.0.1 IP in spam test for registered acconts.
= 5.38.1 2016-03-24 =
* Fixed issue with PHP sessions and 'The session id is too long or contains illegal characters'.
* Removed SpamFireWall protection on /feed page.
* Disabled anti-spam tests for AJAX calls if the option 'Custom contact forms' is turned off.
* Added reject notice for spam submissions on Gravity forms with AJAX calls.
= 5.37.3 2016-03-10 =
* Minor bug fixes. Added an option to support Varnish cache.
= 5.36.1 2016-02-05 =
* Fixed bug, when users receive error after logging in
= 5.36 2016-02-04 =
* Improved JavaScript anti spam protection
* Improvements for avoiding blocking requests from payment systems
= 5.35 2016-01-14 =
* Added support for IP licensing
* Some anti-spam protection improvements
* Small backend interface fixes
= 5.34.1 2015-12-17 =
* Fixed trackback antispam protection: improved checking mechanism
* Fixed problem with blocking MailPoet: added exclusions in spam checking algorithm
= 5.34 2015-12-10 =
* Improved spam checking mechanism
* Added "Collect browser details" option for better antispam protection
* Fixed custom contact forms checking
* Minor translations fixes
= 5.33.1 2015-12-04 =
* Fixed issue with BBPress
* Fixed anti-spam comments checking
* Fixed bulk checking
* Fixed trackback and pingback checking
= 5.33 2015-12-01 =
* Backend interface fixes
* Improved SpamFireWall efficiency
* Improved performance of anti spam checking
= 5.32 2015-11-26 =
* Added improvements for manual spam detection
* Fixed errors in backend
* Fixed bulk users anti spam checking
* Added indicator for bulk spam checking
* Added "Get access key automatically" feature
= 5.31 2015-11-11 =
* Improved backend performance
* Fixed counter of approved/blocked spam attacks
* Fixed Spam Firewall logging
= 5.30 2015-11-05 =
* Improved anti-spam checking
* Optimized performance
* Fixed blocking email preview in MailPoet
* Interface fixes
* WPMU interface fixes
= 5.29 2015-10-27 =
* Optimized performance
* Fixed bugs in custom contact forms spam checking
= 5.28.7 2015-10-23 =
* Major backend peromance fix.
= 5.28 2015-10-16 =
* Fixed errors in anti-spam checking
* Restored options for spam checking registrations and cpmmon contact forms
* Improved anti spam defence
* Fixed problems with AJAX functionality in MailPoet, WooCommerce and other AJAX plugins
= 5.27 2015-10-13 =
* Improvements in SpamFireWall feature
* Code optimization
* Backend interface fixes
= 5.26 2015-10-05 =
* Added WordPress Language Pack support
* Removed spam checking for some autorisation plugins
* New experimental feature: SpamFireWall
= 5.25.2 2015-09-28 =
* Fixed backend bug
= 5.25.1 2015-09-28 =
* Added widget with anti-spam statistics
* Added information about blocked spam attacks in admin dashboard and CleanTalk settings
* Added ability not to check comments for users with 3 or above allowed comments
* Added an option 'Help others known CleanTalk' to show information for site visitors, that your site is protected from spam by us
* Some backend interface settings
* Removed "CleanTalk connection test" query
= 5.24.1 2015-09-16 =
* Fixed some errors in frontend
* Fixed access key saving
= 5.24 2015-09-14 =
* Backend interface fixes
* Improvement for AJAX JavaScript spam checking
= 5.23 2015-09-01 =
* Fixed BuddyPress profile search false positivities of anti-spam protection.
* Some interface fixes of bulk users & comments spam checking
= 5.22 2015-08-26 =
* Fixed possible XSS issue for anti-spam test on third-party forms.
= 5.21 2015-08-21 =
* Fixed bug with skipping spam submissions
* Fixed bug with receiving old user_token for viewing anti-spam statistics
* Small backend fixes
= 5.20 2015-08-15 =
* Fixed anti-spam stats in admin bar
* Fixed issue with skipping spam submissions
* Added some PHP-constants for advanced users
= 5.19 2015-08-11 =
* New feature: anti-spam checking for registered users
* Fixed issue with AJAX JavaScript checking
* Fixed issue with SEO Yoast xml sitemaps.
= 5.18 2015-08-04 =
* Fixed issue with user_token
* Added anti-spam API, see our FAQ
= 5.17 2015-07-23 =
* Fixed infinite redirection after activation
* Minor backend fixes
= 5.16 2015-07-22 =
* Fixed external services checking
* Fixed mass comments deletion
* Fixed AJAX anti-spam protection
= 5.15 2015-07-16 =
* New feature: anti-spam protection for forms, that uses external services
= 5.14 2015-07-03 =
* Added anti-spam protection for some themes and plugins
* Some backend fixes
= 5.13 2015-06-12 =
* Closing notification for anti-spam renew
* Fixed bulk anti spam comment checking
= 5.12 2015-06-01 =
* Added option for checking all post data for spam
* Some JavaScript protection improvements
* Added option for old JavaScript check (without AJAX)
= 5.10 2015-05-25 =
* Fixed Javascript error on some forms
= 5.9 2015-05-21 =
* Fixed Javascript error on CF7 and JetPack
* Some backend and frontent fixes
= 5.8 2015-05-18 =
* Minor fixes
= 5.7 2015-05-18 =
* Fixed French translation
* Fixed protection algorithm
= 5.6 2015-05-11 =
* Fixed translation
* Fixed bulk comments anti-spam checking
* Added option for disabling anti spam statistics in adminbar
* Some security fixes
= 5.5 2015-04-29
* Fixed security issue
= 5.4 2015-04-27 =
* Some interface and functionality changes in plugin settings page
* Added counter for anti-spam statistics in admin bar
= 5.3 2015-04-13 =
* Added anti-spam protection for Divi theme contact forms
* Added anti-spam protection for MyMail contact forms
* Added anti-spam protection for MailPoet Newsletters
* Some interface and functionality changes in backend
= 5.2 2015-04-01 =
* Added link for anti-spam statistics
* Added WP User Frontend Pro registration form protection
= 5.10 2015-03-24 =
* Fixed site crash after installing 5.0 on some websites
= 5.00 2015-03-24 =
* Added bulk comments checking for spam via CleanTalk blacklists
* Added anti-spam form protection for 'Ajax Login & Register'
* Fixed JetPack form protection
= 4.24 2015-03-20 =
Added immediate spam protection activation.
= 4.22 2015-03-17 =
Added button for automatic spam protection key getting.
= 4.21 2015-03-11 =
Added license renew notification.
= 4.20 2015-03-03 =
German, Italian, Polish, Portuguese translations, minor code fixes.
= 4.19 2015-02-24 =
Increased JS keys lifetime.
= 4.18 2015-02-17 =
Bugfix - fixed bug with comments approvement, PayPal 'payment_status' and Akismet 'spam' status processing.
= 4.17 2015-02-12 =
New base class, divided code to 3 separate files - common, public and admin.
= 4.16 2015-02-05 =
New base class, fixed JetPack filters logics, optimized Formidable, bbPress, BuddyPress filters.
= 4.15 2015-01-29 =
Support of Contact Form 7 versions before 3.0.0, fixed global JS-vars and online notice cookie logics.
= 4.14 2015-01-19 =
Removed deprecated option from comment approvement code.
= 4.13 2014-12-29 =
Not spam comments auto approvement bug fix.
= 4.12 2014-12-29 =
Plugin backend minfor bug fixes.
= 4.11 2014-12-22 =
Major changes in spam protection algorithms.
= 4.10 2014-12-10 =
Minor improvements for custom contact/registration/subscribe forms.
= 4.9 2014-11-24 =
Minor bug fix for Contact form 7.
= 4.8 2014-11-19 =
Improved anti-spam protection for BuddyPress registrations and custom contact forms.
= 4.7 2014-11-16 =
Fixed JavaScript antispam test for FastSecure contact form.
= 4.6 2014-11-11 =
Minor changes in anti-spam logic for BuddyPress registrations, contact forms and bbPress guest posting.
= 4.5 2014-11-04 =
Bug fixes for Contact form 7 and bbPress guests posting.
= 4.4 2014-10-29 =
Improved JS checking for CF7.
= 4.2 2014-10-20 =
Increased plugin perfomance for BuddyPress registrations.
= 4.1 2014-10-13 =
Minor anti-spam improvements for contacts, registration and contact forms.
= 4.0 2014-10-06 =
Major anti-spam improvements for registration and contact forms.
= 3.9 2014-10-01 =
Did exception to do not break to create new user in WordPress backend.
= 3.8 2014-09-19 =
Bug fix release. Minor fixes in API class and JavaScript anti-spam test.
= 3.6 2014-09-15 =
Minor fixes in anti-spam protection for Formidable and custom contact forms.
= 3.4 2014-09-04 =
Spam comments rotation. Custom (themes) contact forms support.
= 3.2 2014-08-27 =
Minor changes in spam filtration logic.
= 3.1 2014-08-19 =
Major changes for comments antispam logic. Improved plugin speed.
= 2.59 2014-08-14 =
Antispam protection for bbPress guests posts. Improvement for JetPack comments and PHP API update.
= 2.58 2014-08-06 =
* Added anti-spam protection for signups posted via WooCommerce order form.
* Improved anti-spam protection for Contact Form 7.
* Improved anti-spam protection for registrations. Now the plugin looking for JavaScript antispam test results not only in POST array, but in COOKIES array too. This improvement allows protect signup forms for any untested signups plugins and themes.
* Updated PHP API. No the plugin can resolve sender IP for websites behind proxy servers. If the proxy servers uses private IP address.
= 2.57 2014-07-29 =
* Improved anti-spam protection for comments. The plugin now proccessing website url in the comments form.
* Fixed sign remove logic for approved comments. Previous version doesn't cut sign for comments approved via AJAX call in WordPress backend.
* Fixed switching to SSL for comments. Previous version doesn't use secured connection for comments.
= 2.56 2014-07-21 =
* Fixed account status check logic. Previous version makes unnecessary test API calls when the plugin asks account status check.
= 2.55 2014-07-11 =
* Fixed bug with account status function. In backend the plugin showed notice 'Please don’t forget to disable CAPTCHA if you have it!' on every page.
= 2.54 2014-07-11 =
* Fixed signup anti-spam protection logic for BuddyPress registrations.
* Fixed anti-spam protection for JetPack contact form.
* Changed account status check logic.
= 2.53 2014-06-27 =
* Fixed anit-spam protection bug for signups.
* Changed anti-spam functions (comments and signups) priority.
= 2.52 2014-06-25 =
* Fixed 'Fatal error: Call to a member function get_error_code()' issue with signups via BuddyPress.
= 2.51 2014-06-23 =
* Added spam protection for registrations via plugin New User Approve by Josh Harrison. If the CleanTalk matched signup as spam this signup will be denied to placing in pending queue.
* Added option "Use secure (SSL) connection to CleanTalk cloud". If the option enabled plugin will communicate with CleanTalk severs via 128bit encrypted data channel. So, if you have SSL protected webforms on website you can use this option to be sure that visitors personal data safely transmits to CleanTalk servers.
* Fixed minor bug with loading backend functions.
= 2.49 2014-06-10 =
* Added spam protection for S2Member Auth.net forms.
* Added spam protection for multisite signup form.
* Optimized account status check function.
= 2.46 2014-05-19 =
* Added: HTML notice about the need to enable JavaScript.
* Fixed: Fixed pingbacks anti-spam test.
= 2.44 2014-05-12 =
* Added: Anti-spam protection for S2Member framework.
* Improved: Plugin load time for backend and frontend.
* Improved: JavaScript anti-spam test.
* Fixed: PHP warning mb_convert_encoding()
= 2.42 2014-04-29 =
* Fixed: JavaScript anti-spam test for comments.
= 2.38 2014-03-27 =
* Fixed: Registraion form submit time spam test.
= 2.36 2014-03-12 =
* Reversed to patches from old revisions.
= 2.35 2014-03-12 =
* New: Notifications about disabled account
* New: Improved JavaScript spam test.
* Fixed: Code optimization
* Fixed: JavaScript test for signups.
= 2.33 2014-02-12 =
* Fixed: CURLOPT_FOLLOWLOCATION bug at admin notice
= 2.32 2014-02-04 =
* New: Added notice about automatically approved comment. The notice shows only for first approved comment and only for new commentators (without approved comments) of the blog.
* New: At WordPress console added banner for notices.
* Changed: Screenshots updated.
= 2.31 2014-01-24 =
* New: Added spam protection for JetPack comments
* Fixed: CURL connection issue "Expect: 100-continue"
= 2.30 2014-01-13 =
* Changed: Improved servers connection logic.
* Fixed: Antispam test for Fomidable forms.
= 2.27 2013-12-06 =
* New: Added protection against spam bots for JetPack Contact form.
* Fixed: JavaScript anti-spam logic for registrations and Contact form 7.
= 2.25 2013-11-27 =
* New: Added protection against spam bots for BuddyPress registrations.
* New: Added protection against spam bots for Contact form 7.
* New: Added Spanish (es_ES) translation.
= 2.23 2013-11-20 =
* New: Added automatic training blacklists on spam bot account deletion.
* New: Added URL to project homepage at plugin options.
* Changed: Improved anti-spam logic.
= 2.21 2013-11-13 =
* Changed: WordPress blacklists settings get priority over plugin's anti-spam settings
* Changed: Disabled management approval comments for regular commentators of the blog. Automatically approved for publication only the comments of the new blog authors.
* Changed: PHP code optimizations
= 2.19 2013-11-08 =
* New: Antispam protection from spam bots at the registration form
* Changed: Russian localization for admin panel
* Changed: PHP code optimizations
= 2.5.18 2013-11-01 =
* Fixed: Bug with selection of the last comments for post
* New: Antispam protection for Formiadble feedback forms
* New: Automatic deletion of outdated spam comments
* New: On/Off option for comments spam filtration
* Tested with WordPress 3.7.1
= 2.4.15 2013-09-26 =
* Fixed: Bug with mass comments deletion
* Changed: Russian localization for admin panel
* Tested with mulitsite setup (WordPress network or WPMU)
= 2.4.14 2013-08-29 =
* Changed: Removed feedback requests to the servers for banned (spam) comments.
= 2.4.13 2013-08-19 =
* Fixed: "Fail connect to servers..." error on hostings with disabled 'allow_url_fopen' PHP option.