Spam protection, AntiSpam, FireWall by CleanTalk

Descripción

No CAPTCHA, no questions, no animal counting, no puzzles, no math and no spam bots. Universal AntiSpam plugin.

Características Anti-Spam

  1. Hace parar spam comentarios.
  2. Hace parar spam registros.
  3. Hace parar spam direcciones del correo electrónico.
  4. Hace parar spam órdenes.
  5. Hace parar spam reservas.
  6. Hace parar spam suscripciones.
  7. Stops spam surveys, polls.
  8. Hace parar spam aplicaciones.
  9. Stops spam in WooCommerce.
  10. Comprueba y elimina los comentarios de spam existentes y los usuarios de spam.
  11. Compatible con usuarios y dispositivos móviles.
  12. Compatible con el Reglamento General de Protección de Datos (RGPD) (UE).
  13. Validación de correo electrónico en tiempo real. ¿El correo electrónico es real o no?
  14. Bloqueo de correos electrónicos desechables y temporales.
  15. Sin spam: sin penalizaciones de Google. Dale impulso a tu SEO.
  16. Compatible con móviles, antispam y cortafuegos.
  17. Detiene el spam en el formulario de búsqueda.
  18. Disable comments.
  19. Spam FireWall: Anti-Flood
  20. Spam FireWall: Anti-Crawler
  21. Hide «Website» field for comments

Public reviews

CleanTalk: servicio antispam basado en la nube para mantener Tu sitio libre de bots.
   Reseña de NewsWatch.

Using CleanTalk on WPLift was a great test as we receive huge amounts of spam.
Oliver Dale, WPLift.com.

I 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.com

El punto de venta clave de CleanTalk para mí no es simplemente su efectividad. Es el hecho de que CleanTalk funciona en segundo plano. No hace que los usuarios pasen por alto para enviar un comentario o completar un formulario.
   www.kevinmuldoon.com

Free trial then $8 per year

CleanTalk es un plugin anti-spam gratuito que funciona con el servicio Cloud Anti-Spam premium cleantalk.org. Este plugin como servicio https://en.wikipedia.org/wiki/Software_as_a_service.

Protección Anti-Spam para comentarios

Protección anti-spam nativa para WordPress, comentarios de JetPack y cualquier otro plugins de comentarios. El plugin mueve los comentarios de spam a la carpeta SPAM o puede configurar la opción para prohibir los comentarios de spam silenciosamente. También puede activar la opción en la configuración del plugin para eliminar automáticamente los comentarios de la carpeta SPAM.

Filtro de registros de spam bots

Spam filter for contact forms

Contact Form by WPForms spam filter

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.

Elementor Website Builder filter

Plugin extends spam protection for Elementor Website Builder. It filters spam submisssions and tested for contact form type.

Gravity forms spam filter

Plugin extends spam protection for Gravity forms. It filters spam submisssions for any type of forms.

Formidable Form Builder spam filter

Plugin extends spam protection for Formidable Form Builder. It filters spam submisssions for any type of forms – Contact Form, Survey & Quiz Forms.

Contact Form 7 spam filter

Plugin extends spam protection for Contact Form 7 (CF7). It can be used with any other third-party spam filters.

Ninja forms contact form spam filter

Filtros para correos no deseados en WooCommerce.

Anti-spam por CleanTalk filtra registros de spam y comentarios de spam para WooCommerce. El plugin es totalmente compatible con WooCommerce 2.1 y superior.

Filtro anti spam en boletines

Filtros de spam para formularios de contacto tema

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.

filtro de spam bbPress

Protección contra spam para todo lo relacionado con bbPress: inicios de sesión, registros, foros, debate y respuestas.

Other spam filters

  • WordPress Landing Pages.
  • Portada del usuario WP, usuario Pro.
  • Any WordPress form (checkbox ‘Custom contact forms’).
  • Cualquier presentación al sitio (casilla ‘Comprobar todos los datos de POST’)

Compatible with WordPress cache plugins

Verifica los comentarios existentes en busca de spam. Eliminación en bloque de comentarios de spam. Spam comment Cleaner

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.

Verifica los usuarios existentes en busca de spam. Eliminación en lotes de cuentas de spam. Spam users cleaner

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.

El bloqueo de usuarios por país

Bloquea automáticamente los comentarios y los registros de los países que ha establecido una prohibición para. Esta opción es útil en casos de protección contra el spam manual y para la mejora de la protección. Si su sitio no está destinado para el público internacional y no esperas comentarios/usuarios de otros países.

El bloqueo de los comentarios de acuerdo a «palabras vacías»

Puede bloquear los comentarios que contengan «palabras de detención» para mejorar la protección contra correo no deseado y los mensajes con obsceno bloqueo de palabras. Puede agregar palabras o frases en particular.

Listas negras privadas para el servicio anti-spam

Bloquea automáticamente los comentarios y los registros de tu lista privada de direcciones IP / correo electrónico black. Esta opción ayuda a reforzar la protección contra el spam de un spam manual o bloquear los comentarios no deseados de los usuarios. Puede agregar no sólo ciertas direcciones IP, sino también una subred separada a su lista negra personal.

Private black list for Spam FireWall

Te permite ñadir direcciones IP y subredes individuales a SpamFireWall.
bloquea los ataques de spam de las direcciones IP que aún no están incluidas en la base SFW. Esta opción puede ayudar a bloquear HTTP / HTTPS DDoS, SQL, ataques de fuerza bruta y cualquier otro que lo hizo a través del HTTP / HTTPS. Puedes añadir no sólo ciertas direcciones IP, sino también una subred separada a tu lista negra personal.

Hide «Website» field for comments

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 option is disabled by default and can be enabled in plugin Settings in your WordPress dashboard.

Low false/positive rate

This plugin uses multiple anti-spam tests to filter spam bots having as low false/positive rate as possible. Multiple anti-spam tests help to avoid false/positive blocks of the real website visitors even if one of the tests failed.

¿Qué tan efectivo es CleanTalk?

Bloquear el spam con precisión no es algo fácil de hacer, pero CleanTalk tiene una tasa de Falso/Positivo probada muy baja. Aquí hay estadísticas reales sobre falsos positivos para todos los clientes.

  • Registrations – 0.004%
  • Comments – 0.004%
  • Contact forms – 0.006%
  • Orders (WooCommerce) – 0.016%
  • Site search – 0.001%

La estadística se calculó el 28 de agosto de 2020 para 2.5 millones de solicitudes.

¿Cómo CleanTalk mejora SEO para su sitio web?

So, you already know that the speed of the site has a direct impact on SEO.

CleanTalk funciona más rápido que la mayoría de los otros plugins anti-spam. Es de conocimiento común que contra más rápido se cargue su sitio, mejor será la experiencia del cliente, mejor será su SEO, y mejor se convertirá su sitio. La velocidad es cada vez más importante en SEO, la conversión y la experiencia del usuario. Hoy en día, la velocidad del sitio es uno de los factores de clasificación más importantes de Google. Un sitio que se carga lentamente perderá los visitantes y los ingresos potenciales.

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 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

¿Cómo funciona CleanTalk?

  • A visitor writes a comment or registers
  • Anti-Spam by 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 spam log which can be viewed in the Control Panel service.

CleanTalk team has been developing a cloud antispam system for five years and has created a truly reliable anti-spam service designed for you to guarantee
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.

Spam FireWall

CleanTalk has an advanced option «Spam FireWall». 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.

Spam FireWall es totalmente compatible con los servicios VPN más populares.
Además, Spam FireWall es compatible con todos los motores de búsqueda Google, Bing, Yahoo, Baidu, MSN, Yandex, etc.

How Spam FireWall works?

  • The visitor enters to your web site.
  • HTTP request data are being checked in the nearly 5.8 million of the identified spam bot IPs.
  • If it is an active spam bot, the bot gets a blank page, if it is a visitor then he receives a normal page. This process is completely transparent for the visitors.

Toda la actividad Spam Firewall de CleanTalk se está registrando en el proceso de filtrado.

Spam FireWall DDoS Protection

Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, Spam FireWall blocks all requests from bad IP addresses. Your website gives the intruder a special page with the description of DDoS rejection instead of the website pages. Therefore Spam FireWall helps to reduce CPU usage of your server.

Spam FireWall: Anti-Flood & Anti-Crawler

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

No spam comments, no spam registrations, no spam contact emails, no spam trackbacks. CAPTCHA-free anti-spam for WordPress

Spam is one of the most irritating things. Spam rates are increasing every year and conventional anti-spam can no longer handle all spam bots. CleanTalk prevents and automatically blocks spam. You’ll be surprised how effective CleanTalk is in protecting from spam.

AntiSpam plugin info

CleanTalk is an all-in-one antispam 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. 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 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.

Hemos desarrollado el antispam para WordPress que te protege de los robots de spam al máximo nivel, lo que te permite proporcionar a tus visitantes un formulario simple y conveniente de comentarios/registros sin molestos CAPTCHA y rompecabezas. CleanTalk detecta spam en pruebas de varios niveles, lo que nos permite bloquear hasta el 99,998 % de los robots de spam.
El método antispam ofrecido por CleanTalk evita inconvenientes para los métodos de comunicación (CAPTCHA, pregunta-respuesta, etc.) y ofrece a los visitantes del sitio uno más cómodo.

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:

  • Up to 99.998% protection from spam bots.
  • Time and resources saving.
  • More registrations/comments/visitors.
  • Protección contra el spam de los varios sitios web a la vez en diferentes CMS.
  • Facilidad de instalación y uso.
  • Traffic increase and loyalty to the users.
  • 24/7 technical support.
  • Borrar las estadísticas.
  • Spam FireWall.
  • No captcha (reCaptcha), puzzles, etc.
  • Free mobile app to control anti-spam protection on your website.

Additional features

  • Daily and weekly detailed anti-spam reports: traffic VS spam.
  • Apps para iPhone, Android para controlar el servicio anti-spam, los comentarios, las inscripciones, los contactos, el tráfico y las estadísticas de spam de los últimos 7 días.
  • AntiSpam apps for most popular CMS on cleantalk.org.

How to protect sites from spam bots without CAPTCHA?

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.

Características de CleanTalk

Anti-Spam by CleanTalk with Spam FireWall is one of the fastest plugins that allows you to lower the server load. One of the important parameters for each webmaster is the speed of the site, so we make sure that our plugin consumes as few server resources as possible. The Cloud Service provides the advantage: all data processing takes place in the Cloud.

El equipo de CleanTalk ha desarrollado algoritmos anti spam únicos para evaluar el comportamiento de los visitantes. CleanTalk analiza el comportamiento del usuario y los parámetros de los formularios fill
. Nuestro módulo anti-spam, que se instala en su sitio web, envía los parámetros de comportamiento de un visitante o un bot de spam. Cuando estos parámetros
se calculan, el servicio anti spam toma una decisión: publicar un mensaje o definirlo como spam y rechazarlo. Sobre la base de estas comprobaciones, el servicio forma su propia lista de direcciones de correo electrónico utilizadas por los robots de spam.

Los registros de visitantes se controlarán de forma similar. El servicio se suma a la lista negra no sólo direcciones de correo electrónico, sino también las direcciones IP y dominios de sitios web que promueven a sí mismos a través de correo de spam. Todo esto sucede de forma automática y no requiere ninguna acción por parte de la administración de la página web. En 2,5 millones de consultas al servicio comete un error en 40-45 casos, es decir CleanTalk detecta el spam con 99.9982% de precisión. Monitoreamos constantemente estos errores y realizamos ajustes a nuestros algoritmos. Incluso con esta precisión excepcional de nuestro equipo tiene el objetivo de mejorar las cifras a través del tiempo.

Todo-en-uno. CleanTalk protege todos los formularios de forma instantánea – comentarios, registros, comentarios, contactos. No es necesario instalar plugins adicionales para cada formulario. Ahorrar recursos y aumentar el rendimiento de su sitio web.

Spam attacks log. Anti-Spam by CleanTalk records all filtered comments, registrations 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. The existing comments and users checking process is performed in a database of the nearly 2 million identified spam bots. Detailed spam stats allows CleanTalk customers to fully control it.

CleanTalk has an advanced option «Spam FireWall». This option allows you to block the most active spam bots before they get access to your website. It unloads you website pages when an attempt attack was made, so your web server won’t run unnecessary scripts on these pages. Also it prevents any scanning of website pages by spam bots. Subsequently Spam FireWall significantly reduces your webserver load. Spam FireWall can mitigate HTTP/HTTPS DDoS attacks. When an intruder makes GET requests to attack your website, Spam FireWall 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. Spam FireWall can help to reduce the CPU usage of your server because of this reason.

«El equipo de CleanTalk ha estado desarrollando un sistema de protección de spam en la nube por cinco años y ha creado un servicio anti-spam verdaderamente fiable diseñado para usted y garantizar su seguridad».

Modo marca blanca

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:

  1. Check setting «Enable White Label Mode».
  2. Fill «Hoster API Key» field with key from CleanTalk’s hoster panel.
  3. Fill «Plugin name» field. It could be any name you want for the plugin.
  4. Save settings.

El plugin hará todo lo demás.

Actualización automática de CleanTalk Anti-Spam

CleanTalk Dashboard te permite establecer la actualización automática del plugin y seleccionar varias web y actualizar el plugin de una sola vez en todos los sitios con un solo clic o puedes configurar la actualización automática para todos las web o webs separadas.

Nota: hay 24 horas de retraso antes de que se realice la actualización automática. Este retraso permite evitar cualquier problema. Todas las actualizaciones realizadas a través del escritorio de CleanTalk de forma manual se realizarán de inmediato.

El sistema de actualización automática funcionará desde CleanTalk Anti-Spam versión 5.88

Validación de correo electrónico en tiempo real. ¿El correo electrónico es real o no?

Es muy importante asegurarse de que el usuario haya usado su dirección de correo electrónico real. Los spambots a menudo usan direcciones de correo electrónico falsas, es decir, direcciones que no existen.

CleanTalk verificará la existencia de direcciones de correo electrónico en tiempo real.

Las direcciones de correo electrónico no existentes también conllevan otros problemas para los propietarios de webs.

  • Nunca puedes contactarlos por correo electrónico,
  • el cliente nunca recibirá avisos tuyos (carta de activación de cuenta, recuperación de contraseña, distribución de correo electrónico, avisos, etc.),
  • Si utilizas el marketing por correo electrónico para tus clientes, una gran cantidad de correos electrónicos inexistentes en la lista de correo pueden hacer que tu dirección IP se añada a varias listas negras de servidores de correo electrónico.

Mejora tu lista de correo electrónico con la validación del correo electrónico sin correos electrónicos falsos.

Bloqueo de correos electrónicos desechables y temporales.

Bloquea usuarios falsos y sospechosos con correos electrónicos desechables y temporales para mejorar la entrega del correo electrónico. Por lo tanto, también evita la actividad malintencionada, los bots de spam y los trolls de internet.

Detiene el spam en el formulario de búsqueda.

Los robots de spam pueden usar tu formulario de búsqueda para hacer una solicitud GET con texto de spam.
CleanTalk Anti-Spam tiene la opción de proteger el formulario de búsqueda de tu web de los robots de spam. Cada vez, la búsqueda genera una nueva página y si hay muchas solicitudes, esto puede crear una carga adicional. Entonces, en algunas condiciones, las búsquedas de spam pueden indexarse, lo que afecta al SEO,

  • Spam FireWall bloquea el acceso a todas las páginas de ña web para los robots de spam más activos. Reduce la carga y el tráfico de tu servidor web simplemente haciendo esto.
  • La protección antispam para los formularios de búsqueda de webs repele los robots de spam.
  • Si tu formulario de búsqueda obtiene datos con demasiada frecuencia, el plugin CleanTalk Anti-Spam agregará una pausa y la aumentará con cada nuevo intento de enviar datos. Le ahorra tiempo al procesador de tu servidor web.
  • La protección contra spam te permite no prohibir la indexación de los robots rastreadores si realmente la necesitas, pero al mismo tiempo obtendrás protección contra los robots de spam.

Siempre sabrás qué buscaban los usuarios en tu sitio.

Disable comments

This option disables comments on your site. You can choose one or several options:

  • Disable comments for posts
  • Disable comments for pages
  • Disable comments for media

When using Disables comments, existing comments will not be deleted and will remain on the pages.

Traducciones

  • Albanian (sq_AL) – thanks to fjalaime https://wordpress.org/support/users/fjalaime/
  • Francés (fr_FR) – gracias a Gilles Santacreu http://net-ik.net
  • Español (es_ES) – gracias a Andrew Kurtis y WebHostingHub

Requisitos

WordPress 3.0 al menos. PHP 5 con la función CURL o file_get_contents () y ajustes activados ‘allow_url_fopen’. El plugin es totalmente compatible con PHP 7.

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.

Capturas

  • Los ajustes de anti spam son fáciles de usar.
  • 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 o 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 funciona más rápido que la mayoría de los otros plugins anti-spam.
  • The Dashboard with a map of most spam active countries per your account.
  • El plugin borra/elimina los comentarios de spam existentes y las cuentas de los usuarios.
  • CleanTalk's dashboard update link.
  • Confirmación de actualización automática.
  • Website's options.
  • CleanTalk's dashboard.
  • SpamFireWall log.

Instalación

Instrucciones de instalación

  1. Download, install and activate ‘Anti-spam by CleanTalk’.

  2. Obtener clave de acceso https://cleantalk.org/register

  3. Enter Access key in the settings: WordPress console -> Settings -> Antispam by CleanTalk

  4. Do dummy spam comment (registration or contact message) with email stop_email@example.com. You should see notice: Forbidden. Sender blacklisted.

  5. ¡Hecho! El plug-in está listo para usar.

Guía en vídeo – Instalación del plugin Anti-Spam en WordPress.

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.

¿Cómo se puede configurar el plugin en la versión WPMU?

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');

Hazlo antes de activar el plugin. Si el plugin ya está activado, desactívalo, añade el código y actívalo nuevamente.
Ahora, todos los subsitios tendrán esta clave de acceso.

Manage and control spam protection

Ir al Escritorioen cleantalk.org o usar Android, iPhone anti-spam app para administrar y controlar la protección contra el spam.

FAQ

¿Por qué me envían spam?

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.

Is the anti-spam protection safe for mobile visitors?

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.

What does the plugin do with spam comments?

Spam comments are being moved to SPAM folder by default or you can set the option to ban spam comments silently.

How can I test the anti-spam protection?

Please use the email stop_email@example.com for comments, contacts or signups to see how the anti-spam protection works. Also you can see the logs for the last 7 days at the Control panel or look at the folder «Spam» for banned comments.

Is the plugin effective against spam bots?

The 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.

¿Te protege el plugin de la fuerza bruta, ataques DoS y ataques de spam?

Sí, lo hace. Por favor, activa la opción ‘SpamFirewall’ en la configuración del plugin para proteger tu web de DoS/DDoS, ataques XMLRPC.

How does the plugin stop spam?

Por favor, ten en cuenta – las acciones del administrador no se están comprobando.

The plugin uses several simple tests to stop spammers:

  1. JavaScript anti-spam test. 99% of spam bots don’t have full JavaScript functions support. So, the plugin has the code which can be run by normal visitor and can’t be run by the spam bot.
  2. Correo Electrónico, IP, comprobar la entrada de actividad de spam de dominio. El plugin utiliza la base de datos en línea en la actividad de spam cleantalk.org, que consta de más de 20 millones de registros de actividades spam de los IPs, correo electrónicos, dominios y ASN. Si el IP o el correo electrónico del remitente está en la base de datos, el remitente recibe algunas puntuaciones de spam. Para reducir la tasa de falso/positivo el plugin no sólo utiliza la prueba de lista negra para prohibir los spammers, el remitente será prohibido cuando, y sólo cuando las pruebas múltiples de spam han fracasado.
  3. Comment submit time. Spam bots usually submit the info immediately after the page has been loaded, this happens because spam bots don’t actually fill the web form, they just send $_POST data to the blog. The normal visitor sends the data after several seconds or minutes.

¿El plugin antispam protegerá mi tema?

Yes, it will. The Anti-spam by CleanTalk is compatible with any WordPress theme.

What about pingback, trackback spam?

The plugin passes pingbacks without any checks by default. All trackbacks will be blocked if the sender had spam activity.

¿Puedo utilizar CleanTalk con Akismet?

Sure, you can use CleanTalk with Akismet. In this case you will probably have higher false/positive rate (when legitimate comments/signups are being denied), but you will have stronger anti-spam protection on your website.

¿Es CleanTalk mejor que Akismet?

Please look at this features comparison here https://cleantalk.org/cleantalk-vs-akismet

¿Puedo utilizar CleanTalk para eliminar la espera de comentarios de spam?

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.

How does the plugin find spam in pending comments or registered accounts?

El plugin comprueba todos los comentarios que no son spam en la base de datos de la lista negra y te muestra los remitentes que tienen actividad de spam en otras webs.
Hay algunas diferencias entre la base de datos de lista negra y la API para protegerte de los registros/comentarios de los robots de spam online. Las listas negras muestran todo el historial de la actividad de spam, pero nuestra API (que se usa en las pruebas de spam) también se basa en otros parámetros: último día de actividad, número de ataques de spam durante los últimos días, etc. Estos mecanismos nos ayudan a reducir el número de resultados falsos. Por tanto, no hay nada extraño si algunos correos electrónicos o IPs no se encuentran en las pruebas en lote de los comentarios/cuentas.

Para revisar los comentarios por favor vayan aquí:

WordPress console -> Comments -> Find spam comments

Para revisar los usuarios por favor vayan aquí:

WordPress console -> Users -> Find spam users

Should I use other 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-type anti-spam plugins). In some cases several anti-spam plugins could conflict with each other, so it would be better to use just one plugin.

Is the plugin compatible with WordPress MultiUser (WPMU or WordPress network)?

Yes, the plugin is compatible with WordPress MultiUser. Each blog in multisite environment has individual anti-spam options for the protection from spam bots.

After the installation I noticed that the number of spam attacks has been increased in the stats

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 stats, 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, thus the diversity appears. We seek to provide detailed stats.

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, because the plugin detects sender as a human. So, use special email stop_email@example.com to test the anti-spam functionality or wait a few days to see how the plugin works.

Is it free or paid?

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.

¿Puedo utilizar CleanTalk con plugins de caché?

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.

Does the plugin protect from spam bots if I use forms with third-party services?

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.

¿Es CleanTalk compatible con Cloudflare?

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.

¿ Es CleanTalk compatible con una red de distribución de contenidos (CDN)?

Sí, lo es. CleanTalk funciona con cualquier sistema de CDN, es decir, CloudFlare, MaxCDN, Akamai.

¿Puedo utilizar la funcionalidad de CleanTalk en mis plugins?

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", "stop_email@example.com", "127.0.0.1");
//or for some other messages (contact forms, comments etc.)
$res=ct_test_message("nickname", "stop_email@example.com", "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.

I see two loads of script cleantalk_nocache.js. Why do you use it twice?

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

o

define('CLEANTALK_AJAX_USE_FOOTER_HEADER', false); //false - don't use wp_footer() and wp_header() for including AJAX script, true - use it

¿Puedo añadir exclusiones para algunas páginas de mi sitio?

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

¿Qué No puedo enviar mis datos personales a los servidores CleanTalk?

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

How to test Spam FireWall?

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

¡Atención! El modo de incógnito debe estar activado en tu navegador cuando realizas una prueba. Para activar el modo de incógnito, presiona Ctrl + May + N para los navegadores Chrome, Opera y Safari; presiona Ctrl + May + P para Firefox, Internet Explorer y Microsoft Edge. Una guía completa para habilitar el modo de incógnito está aquí: https://www.wikihow.com/Activate-Incognito-Mode

How can I enter access key in WPMU version?

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.

Why is CleanTalk faster and more reliable than stand-alone solutions?

All anti-spam checks are held in the cloud and don’t overload the web server. The cloud solutions have a huge advantage since the parameters are being compared with information from more than 100,000 websites.

I see a lot of blocked messages with the reason «Forbidden. Please enable JavaScript. Spam sender name.» in my logs

A lot of spam bots can’t perform JavaScript code, so it is one of the important checks and most of the spam bots will be blocked with the reason «Forbidden. Please enable JavaScript. Spam sender name.» All browsers can perform JS code, so real visitors won’t be blocked.

If you or some of your visitors have the error «Forbidden. Enable JavaScript.» please check JavaScript support in your browser and do this JavaScript test at this page: https://cleantalk.org/checkout-javascript-support.

If you think that there is something wrong in the messages blocking, let us know about it. Please submit a support request here: https://cleantalk.org/my/support.

¿Funciona el plug-in con Varnish?

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.

Does the anti-spam plugin work with Accelerated Mobile Pages (AMP)?

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.

¿Cómo cerrar la renovación o el aviso de prueba en el backend de WordPress?

Para cerrar el aviso por favor, guarde la configuración del plugin de nuevo o que se cerrará automáticamente en el plazo de 60 minutos después de la renovación.

I’m using PHP 4.2 version and i’m getting errors related with JSON. Why does it happens?

СleanTalk is no longer supports PHP lower than 5.2 version because the support code have incompatibility with PHP 7 version. Please, upgrade your PHP. If you couldn’t perform that, let us know about it via support ticket here: https://cleantalk.org/my/support.

Should I change anything in the plugin’s settings or in my CleanTalk Control Panel when I switch my website from HTTP to HTTPS or vice versa?

No. You don’t need to change anything in the plugin’s settings or in your CleanTalk Control Panel. The plugin will work regardless of the protocol.

How to use Anti-Spam Log?

The following possibilities are available for you in the Anti-Spam Log:

  • Time period for all spam records you want to see.

  • Filter spam records by their status: Any status, Denied, Approved.

  • Filter spam records by your websites.

  • Filtrar los registros de spam por país de donde provienen.

  • Filtrar los registros de spam por dirección IP, dirección de correo electrónico o nombre de usuario.

  • Opciones disponibles para un registro específico:

    • Details – see item 4 below.
    • Spam/Not Spam – press this string if our system made wrong decision and blocked or approved a registration, a comment ot a contact form submission. More about it here: https://cleantalk.org/faq#feedback_spam
    • Delete – delete a record permanently.
    • Personal blacklists – go to your website Black&White Lists page.
    • Record details: block reason, body of the message, additional caught data.

Spam FireWall and AntiSpam – Networks Blocking

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.

Por favor, lee más aquí
https://cleantalk.org/help/sfw-blocks-networks

Gestión de comentarios de spam

By default, all spam comments are placed in the spam folder, now you can change the way the plugin deals with spam comments:

  1. Move to the Spam folder. All spam comments will be placed to the folder «Spam» in the WordPress Comments section except comments with Stop-Words. Stop-Word comments will be always stored in the «Pending» folder.

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.

  1. 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.

  2. 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.

Los comentarios bloqueados y prohibidos se pueden ver en el registro anti spam aquí: https://cleantalk.org/my/show_requests?int=week

Para administrar las acciones con comentarios de spam, ve al panel de control, selecciona la web para la que deseas cambiar las acciones y ve a «Ajustes» debajo del nombre de la web.

Por favor, lee más aquí:
https://cleantalk.org/help/spam-comment-management

¿Cómo informo un bot de spam perdido o un filtro incorrecto?

Si crees que el servicio ha perdido un bot de spam o un visitante de la web filtrado incorrectamente, puedes avisarnos a través del panel de control Anti-spam. Para hacer esto,
Accede al panel de control https://cleantalk.org/my.
Haz clic en la línea «Acceder» debajo del nombre de tu web.
Cuando marcas un registro como «SPAM», su correo electrónico y dirección IP se añadirán a tu lista negra personal para tu web.
Cuando marcas un registro como «No es SPAM», su correo electrónico y dirección IP se añadirán a tu lista blanca personal para tu web.

Por favor, lea más aquí
https://cleantalk.org/faq#feedback_spam

¿El plugin es rápido?

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.

¿Es compatible el plugin con la RGPD de la UE?

Yes, it is. Please read this article,
https://cleantalk.org/publicoffer#cleantalk_gdpr_compliance

Verificar formularios externos

Si tu web tiene formularios que envían datos a fuentes externas, puedes activar la opción «proteger formularios externos». En este caso, si el plugin determina que el mensaje actual es spam, su acción de formulario será reemplazada temporalmente por su nombre de host actual para evitar el envío de datos falsos a una fuente externa.

Reseñas

15 de octubre de 2021
This looked like it was going to be very good, but after signing up, with no problems during the trial period, issues started to appear, including: - Email address typos or fake email addresses allowed though. - Blocking WordPress site search requests when the requesting IP address is not blacklisted or spammy. - Errors when reporting emails as not spam via the portal. - Communication errors for database updates If you are looking for a reliable and consistent anti-spam and email validation service, this isn't the one. This one is far too buggy.
14 de octubre de 2021
O antiSpam CleanTalk traz a segurança que precisamos para produzir conteúdo e conquistar seguidores e clientes.
9 de octubre de 2021
Before Clean Talk I had to do almost daily maintenance to my sites and as you may understand 2020 and 2021 has not left a lot of spare time. They have blocked a lot of spam for which I'm very grateful! Thanks team.
4 de octubre de 2021
Was getting a ton of spam through Caldera Forms and CleanTalk took care of it in a snap. Just had to install and activate it and off it went. Plus the paid version is way more affordable than Akismet, especially for small single-site proprietors. Note that if you have a cache handler on your site and upgrade your CleanTalk account to a premium version, you'll have to clear all your caches to get it working with the new version.
Leer todas las 2.286 reseñas

Colaboradores y desarrolladores

«Spam protection, AntiSpam, FireWall by CleanTalk» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Spam protection, AntiSpam, FireWall by CleanTalk» ha sido traducido a 18 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Spam protection, AntiSpam, FireWall by CleanTalk» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

5.164.1 Oct 21 2021

  • Fix. SFW. Incompatibility WP-Rocket notice removed.

5.164 Oct 21 2021

  • New: Integration. UsersWP plugin integration implemented.
  • New. SFW. Incompatibility WP-Rocket notice added.
  • New: Settings. Advanced settings navigation implemented.
  • New: Server variables. isSSL method added.
  • Mod: Added the functionality of changing the mail when receiving the key during the initial installation.
  • Mod: Custom admin email. Added minified js and css files
  • Mod: validate api key before save settings for new accounts
  • Mod: Antispam. Comments check. Send feedback with hash:01:url data only if post_info->post_url is empty.
  • Fix: State. Option prefix field is public now.
  • Fix: Using get_option(‘home’) for getting the blog url instead get_option(‘siteurl’).
  • Fix: State. Magic __get notice fixed.
  • Fix. State. Exclamation mark fixed.
  • Fix. Common. Getting REST url fixed.
  • Fix: SFW. Update percents fixed.
  • Fix: DB. isTableExists method fixed.
  • Fix. State. $errors field added.
  • Fix: Server::getDomain(). Fixed regexp.
  • Fix: skip log-in request wpstg.
  • Fix: SFW. Work on hosting licenses fixed.
  • Fix: set prefix_name for cleantalk-icons css.
  • Fix: Helper. Hard use https for the curl requests.
  • Fix: Helper. Home url slash added.
  • Fix: SFW. Using direct updating if remote calls not working.
  • Fix: Settings. Save button z-index added.
  • Fix: Admin bar. Exclamation mark style fixed.
  • Fix: Settings. Api key description on active IP license added.
  • Fix: Sender info. Getting page_url on ajax/rest requests fixed.

5.163.1 Oct 12 2021

  • Fix: Queue. Errors of each try fixed.
  • Fix: SFW. Sleep before deleting tables was reduced.
  • Fix: Queue. Accepted tries argument implemented.

5.163 Oct 07 2021

  • New: State. errorExists method implemented.
  • New: SFW. Disabling SFW when the database was outdated.
  • New: Settings templates. Saving template to the several blogs implemented.
  • New: Settings. WPMS settings always show now.
  • New: WPMS. No show any sub-sites errors on wpms mode 2.
  • New: WPMS. Plugin settings are disabled on sub-sites on wpms mode 2.
  • Mod: Remote Calls using POST instead of GET request type.
  • Mod: Helper. No cache GET parameter renamed.
  • Mod: Cron. Transactions implemented #2.
  • Mod: Settings. «URL Exclusions» description updated.
  • Upd: Getting JS. AJAX handler type selecting updated.
  • Fix: Added lost info about total comments in CommentChecker::ctAjaxInfo
  • Fix: add subscriber to skip list.
  • Fix: Changed the plugin name in the list of plugins when enabling White Label
  • Fix: Changed the plugin name in the admin bar when enabling White Label
  • Fix: Feedback. Comments feedback description fixed.
  • Fix: Hide information about Security in admin bar if it is not main site.
  • Fix: SFW. Error toggle used instead of error add/delete.
  • Fix: Alt cookies. Selecting type of alt cookies bug fixed.
  • Fix: protect logged users in gravity.
  • Fix: Updated the condition for showing a link to the security installation in the admin bar.
  • Fix: reverse condition for WL security link.
  • Fix: WPMS. Addition WL info link fixed.
  • Changed plugin name in plugin settings multisite__white_label__plugin_name.
  • Fix: rename plugin name after search plugins if WL is on.
  • Fix: Renamed Antispam by Cleantalk to Anti-spam by Cleantalk
  • Fix: add elementor-pro to skip save action.
  • Fix: WPMS. Sanitize api key during getting key fixed.
  • Fix: Cron. Cron results errors handling fixed.
  • Fix: WPMS. Migrate old WPMS to the new wpms mode.
  • Fix: WPMS. Using main site data on wpms_mode=2.
  • Fix: Helper. Hard use https for the curl requests.
  • Fix: WPMS. Sanitize network settings fixed.
  • Fix: WPMS. Applying settings for selected blogs fixed.
  • Fix: Getting key. Sync after getting key fixed.

5.162 Sep 23 2021

  • New. SFW. Fall back updating system implemented.
  • New: Integration. Added honeypot wc.
  • New: SFW. Added new status PASS_SFW__BY_STATUS for showing die_page.
  • Upd: Cookies. Alternative cookies types was updated.
  • Upd: Ajax. Finding the right WP directory implemented.
  • Fix: Updater fixed.
  • Fix: Firewall update. Not existing FW table.
  • Fix: State. DB prefix fixed.
  • Fix: WPForms. Excluding from the custom contact forms check.
  • Fix. State. DB prefix definition fixed.
  • Fix: SpamFirewall update. Increasing delay in queue transactions, adding time of the queue task start
  • Fix: State. Show notices fixed.
  • Fix: State. Some logic moved from a loop.
  • Fix: Adding a error if Common/Helper::http_request() couldn’t get HTTP code via get_headers().
  • Fix: SFW. Do not AC checking, if cookies were disabled.
  • Fix: http_request() with preset ‘get_code’ using GET HTTP method instead of HEAD now.
  • Fix: SFW. Direct update DB errors handled.
  • Fix: SFW. Direct update creating temp table errors handled.
  • Fix: SpamFirewall update. SFW_IS_DISABLED is not a error. apbct_sfw_update__init() returns false in this case.
  • Fix: Extended header. Cache-Control: max-age=0 in the /Common/Helper::httpRequest()
  • Fix: Updater. Fixed data__use_static_js_key settings name.
  • Fix: Updater. start ct_account_status_check() if main site in 5.127+ versions
  • Fix: Adding error handling to DB::execute() in ApbctWP\SFW.
  • Fix: Cron. Cron last start flag improved.
  • Fix: Cron. Cron execution cooldown decreased to 2 min.
  • Fix: Adding more info in ‘Unknown’ type error.
  • Fix: Exclude Forminator double requests on multipage form.
  • Fix: Settings. Alt cookies types validating fixed.
  • Fix: Ajax. WP core dir parsing fixed.
  • Fix: Settings. Ajax handler title fixed.

5.161.1 Sep 14 2021

  • Fix. State. Checking empty errors fixed.

5.161 Sep 09 2021

  • Fix: Cleantalk.php. dns_get_record() error handling.
  • Fix: Search form integration. PHP Notice.
  • Fix: Default value for «Alternative Cookie Type» setting.
  • Fix: SpamFirewall. Updating percent output.
  • Fix: SpamFirewall. Omit SFW_IS_DISABLED error.
  • Mod: Admin-bar.
  • Fix: SpamFirewall update.
  • Fix: apbct_log(). Log time.
  • Mod: Debug RC. Servers_connection item added.
  • Mod: apbct_test_connection() moved to cleantalk.php.
  • Fix: skip elementor save template.
  • Fix: skip formidable base check.
  • Fix: remove limit for request in delete all spam users.
  • Mod: apbct_test_connection() improvements.
  • Fix: Helper::http__request() timeout is 15 seconds.
  • New: Helper::http__request() low speed time is 10 seconds.
  • Fix: decbin int type in helper.
  • Fix: add apbct_get_rest_url func.
  • Fix: Error report form Cleantalk.php.
  • Fix: skip sfw check if sfw not updated.
  • Fix. Integration. Enfold theme saving options skip protection.
  • Fix. Integration. Cartflows saving cart skip protection.
  • Fix: getOption return variable.
  • Fix: skip sfw if last_update_time is zero.
  • Fix: skip last_update_time sfw check.
  • Fix: add priority to comment_form_default_fields hook.
  • New. Helper. IP detecting improved.
  • Fix. Helper. Multi-curl timeout added.
  • Upd. SFW. SFW block page updated.
  • Upd. SFW. AC block page updated.
  • Upd. Settings. SFW features settings moved to the separated block.
  • Fix. SFW. Random get parameter for redirecting block page updated.
  • Fix. Settings. SFW features settings description fixed.
  • New: Queue. Transaction system.
  • Fix: skip siteorigin pagebuilder save widget.
  • New: Readme. Hide «Website» field for comments added.
  • Fix. Helper. Async curl timeout increased.
  • Fix. Integration. Blogvault requests skipped.
  • Fix: skip classfields check_email action.
  • Mod: Show real HTTP code in a error during downloading GZ file.
  • Mod: Debug call extended.
  • Mod: Admin notices. Added the ability to hide a banner with notifications for each individual administrator for two weeks.
  • Fix. Settings. Long description output fixed.
  • Fix. Settings. JS debug data removed.
  • Fix. SFW. Deleting fw files folder.
  • Fix: api error handle.
  • Fix: SFW. Added update mode if sfw-updater works with tables.
  • New. WPMS. New multisite logic implemented.
  • Fix: Setting. Select field type fixed.
  • Fix: Сhanged the function delete_all_options() of removing plugin options when fully uninstalled.
  • Fix. WPMS. Hoster API key description fixed.
  • Fix: Admin notices. get_option expression is checking more strictly.
  • New: Helper. Added method for validate date format as ‘Y-m-d’.
  • Fix: SFW. Default FW folder fixed.
  • Fix: SFW. FW folder on the first sync fixed.
  • Fix: SFW. Remove wrong FW folders.
  • Fix: SFW. Refactoring apbct_sfw_update__end_of_update().
  • Mod: apbct_test_connection().
  • Fix: /ApbctWP/API::send_request() with empty result.

5.160.3 Aug 31 2021

  • New: Queue. Transaction system.
  • Fix. SFW. Updating for the new clients fixed.
  • Fix. SFW. Deleting UA file fixed.
  • Fix. SFW. Updating via cron fixed.
  • Fix. SFW. Updating process for multisite fixed.

5.160.2 Aug 26 2021

  • Fix. Pixel. Auto mode fixed.

5.160.1 Aug 6 2021

  • Fix: SpamFirewall update.

5.160 Jul 29 2021

  • New: SFW. SFW alternative cookie implemented.
  • New: SFW. AC alternative cookie implemented.
  • New: SFW. AF alternative cookie implemented.
  • New: Helper. Curl multi wrapper added.
  • New: Queue class implemented.
  • Mod: Changed the processing of the honeypot_field for standard comment.
  • Mod: Added integration for Wishlist Members registration form.
  • Mod: Store visited URLs amount reduces to 5 with 128 symbols by URL.
  • Upd: Public js scripts separated.
  • Upd: SFW. Updating process modified.
  • Fix: Moderate rotating fixed.
  • Fix: SFW. Process file errors handling fixed.
  • Fix: Pluggable. Expression fixed.
  • Fix: Ajax. User detection fixed..
  • Fix: Ajax. Ajax handlers fixed.
  • Fix: IP-detection for Cloudflare CDN.
  • Fix: Skip test for ajax alt_session request.
  • Fix: Set cookies on dashboard pages even if the setting is off.
  • Fix: Ajax. Ajax class fixed.
  • Fix: Users scanner. Remove redundant menu.
  • Fix: Added an exception for the action edd_process_checkout Easy Didgital Downloads plugi
  • Fix: SFW. Changed method for getting addr ip.
  • Fix: Integration. WPForms names gathering fixed.
  • Fix: SFW. Min update interval decreased to 14400 seconds.
  • Fix: Integration. WPForms names gathering fixed.
  • Fix: Cleantalk.php. dns_get_record() error handling.
  • Fix: Search form integration. PHP Notice.
  • Fix: Default value for «Alternative Cookie Type» setting.
  • Fix: SpamFirewall. Omit SFW_IS_DISABLED error.
  • Fix: SpamFirewall. Updating percent output.
  • Fix. Settings templates. Sync after template loading.
  • Fix. SFW. Updating process percents fixed.
  • Fix. Antispam. All headers parameter fixed.

5.159.9 Jul 15 2021

  • Fix. SFW. Updating cooldown increased up to 15 min.
  • Fix. Cron. Next call time set by task updating fixed.
  • Fix. SFW. Reset blacklist array before processing.
  • Fix. SFW. Some errors handling fixed.
  • Fix. SFW. Getting update period from dns fixed.
  • Fix. Ajax. Checking nonce for logged in users fixed.

5.159.8 Jul 07 2021

  • Fix: Fixed the connection error Ajax.php when the site files are in a subfolder.
  • Fix. SFW. Anticrawler redirect detection fixed.
  • Fix. Checking sql before the tables creating.
  • Fix. Updater fixed.
  • Fix: Set alt cookies if sg optimizer is enabled.
  • Fix: Exclusion for GiveWP plugin in apbct-public.js. #2

5.159.7 Jul 01 2021

  • Fix. Updater fixed.

5.159.6 Jun 30 2021

  • New. Rest API request detecting implemented.
  • Upd. SFW. AntiCrawler was disabled for the new installations.
  • Upd. SFW. AntiCrawler option moved to the advanced settings section.
  • Mod: email is taken only from visible fields
  • Mod: remove error message about firewall updating
  • Mod: excluded for test WC_Gateway_Tpay_Basic
  • Fix: Added exclude for happyforms.php in apbct_is_skip_request.
  • Fix: Added an error message in the form response
  • Fix: Skip wpforms general requests because of direct integration.
  • Fix. Integration. Autonami Marketing Automations service request kipped.
  • Fix. Cron. Update task method fixed.
  • Fix. SFW. Prevent updating while SFW is disabled.
  • Fix. Cron. Restoring cron tasks during plugin updating.
  • Fix. SFW. Logs sending used limit.
  • Fix: set correct api_key value for ajax calls.
  • Fix. Frontend widget. The widget layout fixed.
  • Fix. Integration. Formidable preparing data for checking.

5.159.5 Jun 24 2021

  • New: Admin bar. Attention mark added.
  • Upd: Admin notices have been rebuilt.
  • Upd: Integrations with HappyForms updated.
  • Fix: Skip fluentform multistep request.
  • Fix: Correct fluent_form skip name.
  • Fix: Admin notices. Trial and renew notices ID attributes renamed.
  • Fix: Admin bar. Trial notice font color changed.
  • Fix: Admin bar. Show admin bar without api key.
  • Fix: Admin bar. Show attention badge if the api key is empty.
  • Fix: AC. Skip checking on 302 redirects.
  • Fix: Added IF NOT EXISTS after ADD COLUMN in cleantalk-updater.php
  • Fix: Removed ADD PRIMARY KEY from apbct_update_to_5_146_4
  • Fix: Removed apbct_update_to_5_146_4
  • Fix: Checking output parameters of API-method get_2s_blacklists_db.
  • Fix: SFW. Writing exclusions fixed.
  • Fix: Integration. GF names detection fixed.
  • Fix: Integration. WPForms nicknames detecting fixed.
  • Fix. SFW. Updating fixed.
  • Fix: Excluding REST API requests from check.
  • Fix. Admin notices. Incompatibility notice fixed.
  • Fix. Compatibility. Notice saving fixed.
  • Fix. Compatibility. Prevent disabling SFW on incompatibility detected.
  • Fix. Compatibility. SFW option is no longer disabled on incompatibility detected.
  • Fix. Admin bar. Reset counters fixed.

5.159.4 Jun 17 2021

  • Fix: Admin bar. PHP error.

5.159.3 Jun 15 2021

  • Fix: Admin bar. Conflict with previous version of Security by Cleantalk.

5.159.2 Jun 15 2021

  • Fix. Renew notice banner shows only on cleantalk pages.
  • Fix. SFW updating. Getting remote data error handling fixed.
  • Upd. Readme updated.
  • Fix. SFW. Auto-updating fixed.
  • Fix: Admin bar style. Install link is no longer highlighted.
  • Fix: Admin bar style. Style for security icon.
  • Fix: Admin bar. Reset buttons counters leads to the same page.
  • Fix. Manual register link fixed.
  • Fix: do not display errors on subsites when wl is enabled.
  • Fix: Admin bar. Rapid fix.
  • Fix. Skipping. WPForms check restricted email request skipped.
  • Fix. Helper. CURL request timeout increased.
  • Fix. Comments/users checker. Description fixed.
  • Fix. Get fields any. Preset nickname parameter fixed.
  • Fix: wpms settings.

5.159.1 Jun 10 2021

  • Fix: Cron. Cron calling in cleantalk-updater.php fixed.

5.159 Jun 10 2021

  • New. Admin Bar. Common admin bar implemented.
  • New: email check before post.
  • New: New admin bar style.
  • New. SFW. Updating integrity control implemented.
  • New. Custom Ajax. Email checking before post.
  • New. Custom Ajax. Getting JS key.
  • New. Custom Ajax. Alternative cookies.
  • Upd. Integrations. Support multiple non-ajax hooks.
  • Upd. Cron. Cron class and cron usage updated.
  • Upd. Pixel. Pixel setting is «auto» for the new installations.
  • Upd. Users checker. Users with completed WC orders no checked.
  • Upd. WPMS settings.
  • Mod. limiting the size of an array top5_spam_ip to five elements in widget.
  • Mod. update data__pixel title.
  • Mod. Update data__use_static_js_key title.
  • Mod. add ‘relative’ parameter in admin_url() for getting ajaxurl.
  • Mod. update field name honeypot_field, reverse logic
  • Mod. changed website field from comments form: type text, display none.
  • Fix. resolve conflict with wiloke theme and unknown plugin, that removes standard authorization cookies.
  • Fix. moved the wiloke_theme options_ajax_save_skip check to apbct_is_skip_request function.
  • Fix. added a theme check along with a hook wiloke_themeoptions_ajax_save_skip.
  • Fix. Integration. Essentials addons for elementor integration fixed.
  • Fix. AC/AF. Clearing AC table via cron fixed.
  • Fix. SFW. Obtaining the count of the networks was fixed.
  • Fix. Cron. Last cron start fixed.
  • Fix. cookies for login page.
  • Fix. Firewall. Update. Filtering bad data.
  • Fix. Custom Ajax. Localized login scripts.
  • Fix. API. Cleantalk\ApbctWP\API fixed to work on SHORTINIT mode.
  • Fix. Custom Ajax. Getting JS key – removed WP ajax hooks.
  • Fix. GetFieldsAny. Bypassing collecting email and names logic fixed.
  • Fix. New admin bar style. Sorting plugins by Alphabet.
  • Fix. ct_get_admin_email return network email if set.
  • Fix. Fixed the name of the key containing the file address to check the number of records.
  • Fix. Comments checker. Non-checkable users tab removed.
  • Fix. Visible fields. Formidable visible fields collecting fixed.
  • Fix. Get fields any fixed.
  • Fix. empty key error for hosting.
  • Fix. WPMS. Api key saving fixed.
  • Fix. WPMS. Network settings saving fixed.
  • Fix. WPMS. Plugin name setting field is not required now.
  • Fix. Alt sessions js fixed.

5.158 May 27 2021

  • Fix: Firewall. SQL-request error.

5.158 May 26 2021

  • New. Integration. WP Foro register system integration.
  • New. Integration. Elementor essentials LoginRegister integration implemented.
  • New: SQL-schema and updater for extended SpamFirewall logs.
  • New: Extended SpamFirewall logs.
  • New: Pixel.
  • Mod: Few improvements to SFW update.
  • Mod: add settings for hidding website field from comment form.
  • Mod: Few improvements to SFW update #2.
  • Mod: Possibility to send empty JSON object in API.
  • Mod: Extended SpamFirewall logs for AntiCrawler module.
  • Upd: SFW. Direct updating method implemented.
  • Upd. Settings. Network settings templates updated.
  • Upd: Firewall. Improvements to update system.
  • Upd: Firewall. Improvements to update system.
  • Fix: replace wp_die to die in ct_die(), refactoring ct_die()
  • Fix. Forms. Exclude field wp-editor-area from collecting visible fields.
  • Fix. Widget. Widget content logic fixed.
  • Fix: Forms. Nicknames detecting fixed #2.
  • Fix: Forms. Getting check_js key fixed.
  • Fix: update ct_die_extended() as ct_die().
  • Fix. Code. Getting delay before js code get if async option enabled.
  • Fix. WPMU. Blog id added in settings templates list.
  • Fix. Integration. Elementor essentials LoginRegister login form protection skipped.
  • Fix. WPMU. Blog id added in settings templates list.
  • Fix. Readme. Required PHP version increased to 5.6.
  • Fix. Updater. 5_157_10 updating fixed #2.
  • Fix. JS. DOMContentLoaded used instead jQuery(document).ready().
  • Fix: SpamFirewall. Update. «FW UPDATE INIT: KEY_EMPTY», «SFW UPDATE INIT: KEY_IS_NOT_VALID» errors.
  • Fix. Users checker. Export to the csv fixed.
  • Fix: SpamFirewall. Update. Error «WRONG_UPDATE_ID».
  • Fix: SpamFirewall. Update. «FW UPDATE INIT: KEY_EMPTY», «SFW UPDATE INIT: KEY_IS_NOT_VALID» errors.
  • Fix: SpamFirewall. Update. Error «WRONG_UPDATE_ID».
  • Fix: \Cleantalk\Common\Helper::http__request() consider only boolean false (empty string » considering as good) as bad response.
  • Fix: SpamFirewall. Update.
  • Fix: SpamFirewall. Update #2.
  • Fix: WPMS empty apikey in options
  • Fix: «Mod: add settings for hidding website field from comment form».
  • Fix: Common/Helper::http__get_headers() fixed.
  • Fix: SpamFirewall admin bar counter.
  • Fix: «Fix: Common/Helper::http__get_headers() fixed.»
  • Fix: Pixel.
  • Fix: «Pixel» setting description.
  • Fix: Extended SpamFirewall logs for AntiCrawler module.
  • Fix: Extended SpamFirewall logs for AntiCrawler module #2.
  • Fix: WPFroms. PHP notice.
  • Fix: Gravity Forms. PHP notice.
  • Revert: Fix: Code. get_fields_any() notice fixed.

5.157.2 May 05 2021

  • Fix: Code. get_fields_any() notice fixed.
  • Fix: Integration. Gravity Forms integration fixed.
  • Fix: Forms. Nicknames detecting fixed.

5.157.1 Apr 29 2021

  • Mod: \Cleantalk\ApbctWP\Variables\Cookie::get() now has ‘cast_to’ param. If defined trying to cast to a given type.
  • Fix: \Cleantalk\ApbctWP\Variables\Cookie::get() calls using ‘cast_to’ param if needed.

5.157 Apr 28 2021

  • New: Invisible fields collecting implemented.
  • New: A dev and a fix version suffix support.
  • New: Variables. Cookie::set() method added.
  • New: Split Cleantalk\Common\DB::method__private_list_add__sfw_wl() in two Cleantalk\Common\DB::method__private_list_add() and Cleantalk\ApbctWP\DB::method__private_list_add__sfw_wl().
  • New: Split Cleantalk\ApbctWP\Helper::http__request__rc_to_host() in two Cleantalk\ApbctWP\Helper::http__request__rc_to_host() and Cleantalk\ApbctWP\Helper::http__request__rc_to_host__test().
  • New: Updater script for 5.157.
  • New: Update/delete SpamFireWall database when it enable/disable. Improvements.
  • New: \Cleantalk\ApbctWP\Variables::AltSessions class.
  • New: «Set cookies» setting now has 3 options «On», «Off» and «Use alternative mechanism for cookies».
  • New: REST API route ‘/alt_sessions’ and callbacks.
  • Mod: Compatibility with Thrive Leads – remove deleted the modal window about successful sending when blocking the user.
  • Mod: changed the handling of gravityform fields, added a check for the visibility of the field when processing the name.
  • Mod: Added a setting for Woocommerce, which includes checking the un-logged user when adding an item to the cart. If the user does not pass the verification, the product is not added to the cart.
  • Mod: Added a settings for Woocommerce – correction.
  • Mod: WC add to cart – change settings description.
  • Mod: Cleantalk\ApbctWP\RemoteCalls::debug() improved.
  • Mod: SpaFirewall update.
  • Mod: add buddypress integration for user account personal data.
  • Mod: Moving \Cleantalk\Common\Helper::apbct_cookie__set() to \Cleantalk\ApbctWP\Variables::set() function.
  • Mod: Using \Cleantalk\ApbctWP\Variables::set() instead of \Cleantalk\Common\Helper::apbct_cookie__set().
  • Mod: Extend \Cleantalk\ApbctWP\Variables to use alternative sessions.
  • Mod: Using \Cleantalk\ApbctWP\Variables\AltSessions class instead of set of «apbct_alt_sessions__» functions.
  • Mod: added loading of country flags from the plugin.
  • Mod: added styles for the widget with anti-spam statistics.
  • Mod: Improving ct_enqueue_scripts_public().
  • Mod: Update for JS ctSetCookie().
  • Mod: AltSessions and Cookie using ‘data__set_cookies’ and ‘data__set_cookies’ settings.
  • Mod: Minified JS updated.
  • Upd: Setting cookies updating.
  • Upd: Setting cookies by JS updating.
  • Fix: SFW. DB result handling.
  • Fix: Integration. Avada theme settings saving fixed.
  • Fix: Cleantalk modal. Layout fixed.
  • Fix: Possible use an html on ajax forms blocking message.
  • Fix: Include JS logic fixed.
  • Fix: Refactoring. Collecting details about browser refactored.
  • Fix: Refactoring. Alert replacing by console log on REST request handling.
  • Fix: Integration. Gravity Forms integration fixed.
  • Fix: ignoring the hidden fields with name if visible fields exists.
  • Fix: Integration. Formidable multi-step form protection fixed.
  • Fix: add max z-index for #cleantalk-modal-overlay.
  • Fix: Cannot read property ‘response_type’ of undefined – xhr.responseJSON – undefined where action wc_add_to_cart_block.
  • Fix: Helper. Set cookies method is deprecated now.
  • Fix: Adding admin IP to whitelist during the login in and plugin activation.
  • Fix: SpamFirewall. Don’t set cookies if option is disabled.
  • Fix: Sorting methods modifiers in \Cleantalk\Common\Helper and \Cleantalk\ApbctWP\Helper classes.
  • Fix: Using \Cleantalk\ApbctWP\Variables\Cookies.
  • Fix: A dev and a fix version suffix support.
  • Fix: Adding admin IP to whitelist during the login in and plugin activation.
  • Fix: New setting ‘Alternative cookies handler type’.
  • Fix: sender_info params.
  • Fix: SpamFirewall deleting 127.0.0.1 from local base during update on local website.
  • Fix: apbct_js_test() considering «Alternative cookie» setting.
  • Fix: Cleantalk\ApbctWP\VariablesCookie::set() automatically set secure flag if null passed.
  • Fix: Check JS via Cookie with the Alternative Cookie on.
  • Fix: Automatically set «secure» param when setcookie() called.
  • Fix: ‘Alternative cookies handler type’ setting layout.
  • Fix: For legacy apbct__hook__wp_logout__delete_trial_notice_cookie().
  • Fix: Cleantalk\ApbctWP\Variables::set_fromRemote(), Cleantalk\ApbctWP\Variables::get_fromRemote() fix parameter type.
  • Fix: SpamFirewall add admin IP when login in or activate plugin.
  • Fix: Dashboard widget. Showing default Cleantalk’s flag if country not found.
  • Fix: Dashboard widget. Showing ‘Unknown’ country name if country not found.
  • Del: Unused apbct_cookie__set() function.
  • Del: «Use alternative mechanism for cookies» setting.
  • Del: «Use cookies less sessions» setting.

5.156 Apr 15 2021

  • New: ApbctWP\RemoteCalls::action__debug().
  • New: ApbctWP\Helper::http__get_data_from_remote_gz__and_parse_csv();
  • New: ApbctWP\Helper::http__get_data_from_remote_gz();
  • New: Update/delete SpamFireWall database when it enable/disable.
  • New: \Cleantalk\Common\DNS class. Allows to get with DNS records and theirs different parameters.
  • New: No cookies if disabled from frontend. Alternative cookies if enabled from frontend.
  • New: \Cleantalk\ApbctWP\Variables\Cookie extends Cleantalk\Common\Variables\Cookie and automatically supports alternative cookies.
  • Mod: Don’t use alternative cookies for JS cookies for now.
  • Mod: ApbctWP\State default data.
  • Mod: Small code improvements.
  • Mod: Minor code improvements.
  • Mod: Using apbct_sfw_update__init instead() of ct_sfw_update().
  • Mod: Updater script to 5.156.
  • Upd: \Cleantalk\ApbctWP\RemoteCalls.
  • Upd: *.min. files update.
  • Upd: Current moderate*.cleantalk.org IP servers update.
  • Refactor: SpamFireWall update.
  • Fix: ApbctWP\RemoteCalls::action__sfw_update().
  • Fix: \Cleantalk\Common\DNS could request specific DNS type record.
  • Fix: Anti Spam. External forms protection capturing buffer fixed.
  • Fix: SFW. Notices disabled on blocking pages.
  • Fix: Admin ajax handler fixed – alert removed.
  • Fix: No alert when error fires.
  • Fix: Notice. change ‘wpms__allow_custom_settings’ to ‘multisite__allow_custom_settings’ in cleantalk-admin.php.
  • Fix: Getting JS key by ajax fixed.
  • Fix: No alert when AJAX fails.
  • Fix: Send plugin version as parameter when apbct-public.min.js script attaching.
  • Fix: The AJAX REST API error text unique.
  • Fix: No alert message when AJAX (REST) error happens.
  • Fix: Skip. MyListing theme service requests skip.
  • Fix: \Cleantalk\ApbctWP\Helper::http__request__rc_to_host(). Considering empty response as error.
  • Fix: \Cleantalk\Common\Helper::http__request(). Empty error while SFW update.
  • Fix: REST API. Required parameter added.
  • Fix: PHP Notices and Warnings.
  • Fix: AntiCrawler UA update.
  • Fix: JS and CSS minified.
  • Fix: ApbctWP\State __get using &. *

5.155.2 Apr 6 2021

  • Fix: Renaming setting to their original names in old update scripts.
  • Fix: Ajax forms protection response fixed.
  • Fix: No alert message when AJAX error happens.

5.155.1 Apr 2 2021

  • Fix: Using WP Rest API.
  • Rollback: Show response for all AJAX forms.

5.155 Mar 31 2021

  • New: Debug. Check connection to API servers.
  • New: Integration. Avada Form Builder.
  • New: Integration. Forminator integration implemented.
  • New: Users checker. Non-checked users tab added.
  • New: SFW. Admin IP will be whitelisted automatically.
  • Mod: Replace «bad» users/comments to «non-checkable».
  • Mod: DisableComments. Disable all comments means disable all comments for any post type.
  • Udp: Setting templates. Product ID support implemented.
  • Udp: Settings. Reorder links actions buttons.
  • Upd: Common. Getting check_js updated.
  • Upd: SFW. Description updated.
  • Fix: Reversed URL exclusions.
  • Fix: Settings. Sync button success ico fixed.
  • Fix: Show response for all AJAX forms #3.
  • Fix: GDPR. Warning text output.
  • Fix: Integration class consider settings.
  • Fix: Exclusions. URL exclusions fixed.
  • Fix: Services Templates. Getting templates optimized.
  • Fix: Services Templates. Possible XSS fixed.
  • Fix: Services Templates. Design layout fixed.
  • Fix: Family of settings comments__disable_comments__* dependencies.
  • Fix: DisableComments class. Media post type includes ‘attachment’ type.
  • Fix: Exclusion for Thrive Ultimatum.
  • Fix: Common/Helper::http__get_headers() ignores empty header name parts.
  • Fix: Exclusion for GiveWP plugin in apbct-public.js.
  • Fix: Do not consider 501 as correct HTTP response code when getting FW data files.
  • Fix: AntiCrawler::update(). Correct error codes.
  • Fix: ApbctWP\Firewall\SFW::update(). Correct URLs for FILE with protocol.
  • Fix: PHP 8 deprecated notices.
  • Fix: Settings. Reversed dependencies. Applies to WooCommerce and Disable Comments settings.
  • Fix: DisableComments::template__check() returns the correct number of comments for enabled types of posts.
  • Fix: DisableComments class. Visibility of some methods.
  • Exception: Paid Memberships Pro – Login Form.
  • Fix: Exception the SFW check for queries with ‘/favicon.ico’ string.

5.154 Mar 17 2021

  • New: Settings Templates functionality implemented.
  • New: SFW. Anti-flood protection uses UA lists for filtration.
  • Fix: Forms. Getting check_js delay removed.
  • Fix: Forms. Rotation check_js fixed.
  • Fix: Integration. Newspaper-theme login form protection skipped.
  • Fix: Integration. Newspaper-theme reset password form protection skipped.
  • Fix: Forms. Gravity Forms paypal addon processing skipped.
  • Fix: Exclusion for wpDiscuz – Online Users Addon.
  • Fix: Remote Calls. Wrapper http__request__rc_to_host() don’t get an array
  • Fix: JS. Modal window fixed.
  • Fix: JS. Show AJAX result fixed.
  • Fix: Skip. Save abandoned cart checking skip.
  • Fix: Skip. SUMODISCOUNT discout request skip.
  • Fix: Skip. WP eMember login form skip.
  • Fix: SFW. Do not cache constants added.
  • Fix: SFW. AC/AF logging fixed.

5.153.7 Mar 15 2021

  • Fix: SFW. Updating fixed.

5.153.6 Mar 12 2021

  • Fix: Show response for all AJAX forms #2.

5.153.5 Mar 10 2021

  • Fix: Show response for all AJAX forms.

5.153.4 Mar 10 2021

  • New: SFW. Log could be sent not more often than 3 minutes.
  • New: SFW. Possibility to use DELETE instead of TRUNCATE to delete SFW log.
  • New: Show response for all AJAX forms.
  • Fix: SFW. Sending log. Committing transaction after TRUNCATE log table.
  • Fix: Integration. CF7 different versions compatibility fixed.
  • Fix: Exclusion for WooCommerce.
  • Fix: Possible SQL-injections fixed.

5.153.3 Feb 25 2021

  • Fix: Security. Preparing UA string for writing to the DB.

5.153.2 Feb 25 2021

  • Fix: Integration. Registration on WICITY theme.
  • Fix: Integration. Registration on Paid Memberships Pro
  • Fix: IP detection.
  • Fix: Error: SFW_DISABLED.
  • Fix: Formidable form. Error with sophisticated field types.
  • Fix: Remote Calls. Cooldown checking for the SFW update fixed.
  • Fix: easy-login-woocommerce requests exclusion fixed.
  • Fix: Jackmail plugin. Skip all admin-side actions.
  • Fix: Remote Calls. Unused deactivation option removed.
  • Fix: Users checker. Last check date fixed.
  • Fix: Users checker. Total users count description fixed.

5.153.1 Feb 20 2021

  • Fix: CF7. Modified spam hook #2

5.153 Feb 17 2021

  • New: Integrations. WPDiscuz integration implemented.
  • New: Using custom modal message instead allert.
  • New: JS cleantalk-modal added.
  • New: Cleantalk\ApbctWP\RemoteCalls class.
  • New: Remote calls using Cleantalk\ApbctWP\RemoteCalls class.
  • New: Cleantalk\ApbctWP\Helper::http__request__rc_to_host(). Wrapper to using RC to the website itself. Makes testing RC before make main.
  • New: Cleantalk\ApbctWP\State::error_toggle().
  • New: SFW update. Make test RC before main.
  • Udp: Integrations. Support several hooks for one integration.
  • Fix: Users. Feedback sending via deleting user fixed.
  • Fix: Users checker. Feedback sending via deleting user fixed.
  • Fix: IP detection.
  • Fix: Users scan. Confirmation message fixed.
  • Fix: SFW. The anti-flood option moved to the advanced settings.
  • Fix: SFW. Show the right url on block page for WPMS.
  • Fix: SFW. The anti-crawler option description fixed.
  • Fix: SFW. The anti-flood option description fixed.
  • Fix: SFW. AC checking on login page fixed.
  • Fix: CF7. Modified spam hook.
  • Fix: SFW. send_logs returning error.
  • Fix: Cleantalk class fixed.
  • Fix: Clearing errors storage before sync.
  • Fix: Clearing SFW errors on updating to 5.151.6.
  • Fix: Updater. Support updating for versions without fix number implemented.
  • Fix: «Email Before Download» plugin request will be skipped.
  • Fix: SFW. Auto-updating option fixed for multisite activation.
  • Fix: Exception for Xoo login form.
  • Fix: Users deleting feedback fixed.

5.152.5 Feb 04 2021

  • Fix: SFW. Auto-updating interval decreased to 5 mins.
  • Fix: Divi. Skip saving epanel.
  • New: Find users/comments table. Add footer description.
  • Fix: SFW. UA option removed.
  • Fix: SFW. AC checking by UA enabled by default.
  • Fix: SFW. AF disabled by default for the new installations.

5.152.4 Feb 01 2021

  • Fix: Cron tasks compare fixed.

5.152.3 Jan 31 2021

  • Fix: Error: SFW_DISABLED.
  • Fix: Moderate connection timeout increased to 6sec.
  • Fix: SFW uses the right API class.

5.152.2 Jan 30 2021

  • Fix: API-requests.

5.152.1 Jan 29 2021

  • Fix: Errors in IP detection.

5.152 Jan 29 2021

  • Fix: Using server protocol for AC checking.
  • Fix: Prevent caching db queries for SFW.
  • Fix: mgm registration temp fix.
  • Upd: Checking skipped request replaced.
  • Fix: Bookly plugin service requests checking skipped.
  • Fix: Youzier login form skipped.
  • Fix: InJob theme lost password skipped.
  • Upd: Showing plugin version on SFW block page.
  • Fix: fix request id rotation.
  • Mod: Show «Insert users» button only for local web servers.
  • Upd: Checking skipped request replaced for non-ajax requests.
  • Fix: BuddyPress edit profile checking skippped.
  • Fix: Unused code removed.
  • Upd: Helper::ip__get() method updated.
  • Fix: UltimateMember password reset skipped.
  • Del: Unused code removed.
  • New: Server::get() now can accept ‘URI’ as an parameter. Returns full URI like ‘http://domain.net/request/path?parameter=value#fragment
  • Mod: apbct_exclusions_check__url__reversed() simplifed and PHPDoc’ed.
  • Mod: apbct_base_call exclusions revised.
  • Mod: $cleantalk_executed chaos simplified.
  • Upd: Shedule sfw update once again if it failed.
  • Fix: Delete cleantalk options via uninstalling.
  • Fix: Deleting table for network sites fixed.
  • Fix: Using host header for AC checking.
  • Fix: Expression formatting fixed.
  • Mod: Cron. Do not runs when it already runs.
  • Mod: Cron class updated.

5.151.4 Jan 18 2021

  • Fix: Users checking performance fix.
  • Fix: AC disabled if SFW contains less than 50 entries.

5.151.3 Jan 15 2021

  • Fix: Prevent logging false blocking for whitelisted networks.
  • Integration: Rafflepress integration implemented.
  • Fix: AF limit increased to 20 by default.
  • Fix: skip Sumo waitlist internal request.
  • Fix: skip raq internal request.
  • Fix: check comments number if comment email exists.
  • New: Schema class added.
  • Fix: SFW – Creation sfw table if not exist.
  • Fix: Updater – Creation sfw table if not exist.
  • New: Schema class used.
  • New: AC disabled if networks count is 0.
  • Fix: SFW updating id getting fixed.
  • Fix: SFW networks counter fixed.
  • Fix: Deleting options fixed.

Early changelogs look in changelog.txt