Descripción
Protege todos tus formularios y accesos contra spam y ataques de fuerza bruta. El plugin es invisible y cumple con GDPR (RGPD, DSGVO). Tiene muchas opciones por un lado y viene con una configuración por defecto bien equilibrada. Por lo tanto, comienza a funcionar muy bien, tan pronto como se activa.
Características clave
- Bloquea el spam en todos (!) formularios públicos, comentarios y accesos
- Invisible. No se requiere entrada del usuario
- Seguir recibiendo el cien por cien de las solicitudes reales
- Cumple con la RGPD (respectivamente DSGVO, RGPD)
- El plugin es gratis
- Sin seguimiento, sin cookies, sin sesiones
- Sin recursos externos
- Fácil de usar
- Amigable con SEO
- Solo código necesario
- Opcionalmente, los mensajes se pueden marcar en lugar de bloquearlos.
Ejemplos de WordPress
- Formulario de acceso
- Formulario de registro
- Formulario de restablecimiento de contraseña
- Formulario de comentarios
Ejemplos WooCommerce
- Finalizar pago
- Formulario de acceso
- Formulario de registro
- Formulario de restablecimiento de contraseña
- Formulario de comentarios
- Formulario de evaluación del producto
Ejemplos de otros plugins
- Forminator
- Thrive Architect & Thrive Apprentice
- WPForms
- Fluent Forms
- Contact Form 7
- Gravity Forms
- Formidable Forms
- Elementor Pro Forms
- Mailchimp for WordPress Forms
- BuddyPress Registration Form
- bbPress Create Topic & Reply Forms
- Ultimate Member Forms
- formulario de comentarios personalizados de wpDiscuz
- Easy Digital Downloads Forms
- Paid Memberships Pro Forms
- MemberPress Forms
- WP-Members Forms
- WP User Frontend Forms
- CheckoutWC & Flux Checkout
- Divi Forms
- Ninja Forms
- Jetpack Forms
- Everest Forms
¡Gracias!
¡Espero que disfrutes utilizando el plugin CAPTCHA! Si estás contento con él, me encantaría recibir tu reseña y quizás también un café.
Instalación
- Instala y activa el plugin a través de la página de plugins de WordPress. ¡Hecho!
- Opcionalmente: después de la activación, puedes ajustar con precisión cómo se bloquearán, marcarán o guardarán los mensajes en el menú de ajustes del plugin.
- You should take a look into the message inbox. As many system functions act like bots, it may happen that they are blocked too. From the inbox and from the spam inbox you can jsut whitelist them with one click respectively.
FAQ
-
Los envíos se tratan incorrectamente como spam
-
- The problem occasionally occurs right after installation due to caching. In such cases, the necessary JavaScript for proof-of-work isn’t loaded as intended. To resolve this, clear the cache on your webserver (WordPress caching is typically managed by plugins, which offer an option to clear the cache) and in your browser.
- JavaScript might crash due to incompatibility between this plugin and another one you’re using. If you notice this, please report it to me. I usually address such issues within the same day. Additionally, it’s crucial to ensure that JavaScript is functioning correctly on all your pages, even without this plugin. In most browsers, you can identify JavaScript errors by pressing F12 on your page and navigating to the console. Here, you can observe what’s happening on your page.
- Generally, I recommend running the plugin in Explicit mode 🎯 as it’s more efficient and avoids compatibility problems. Please refer to the «help» section for this option.
-
Ni los mensajes, ni el spam se muestran en la bandeja de entrada
-
- Activate the Analysis mode 🔍, submit the form and look for the message that has been saved for the new submission. Open the message Check enhance the spam check scope for this type of submission. In general I recommend to run the plugin in the Explicit mode 🎯 and to do so with all types of submissions that you which to be considered for the spam check.
If none of these: If you recognize this behaviour, I would be glad if you gave me a notice in the support forum and usually I would ad specific support for your form-builder.
- Activate the Analysis mode 🔍, submit the form and look for the message that has been saved for the new submission. Open the message Check enhance the spam check scope for this type of submission. In general I recommend to run the plugin in the Explicit mode 🎯 and to do so with all types of submissions that you which to be considered for the spam check.
-
Problems with WooCommerce/ Jetpack activation
-
If you face problems with the activation of Jetpack this may occur during the handshake-procedure of jetpack. This procedure acts like a bot, when it passes a passphrase from a certain IP adress to an automatically generated form on your site.
In order to get this fixed, you need either to disable the option 🖥️ Apply on REST-API, or to whitelist the respective form that is used to exchange the passphrase.
Usually you need to process the following steps for whitelisting:
1. Check the spam folder for the respective message that has been blocked
2. Copy the site-adress «from_site»
3. Paste the site-adress into the option 📄 Site-Whitelist on the properties site
4. Press save
Usually you need to whitelist two different sites to connect jetpack:
1. To connect the site: your-domnain-without-protocol/?rest_route=/jetpack/v4/verify_registration/
2. To connect your user: your-domnain-without-protocol/?rest_route=/jetpack/v4/remote_authorize/
Generally, I recommend running the plugin in Explicit mode 🎯 as it’s more efficient and avoids such compatibility problems. Please refer to the «help» section for this option. -
Problems with activation/ installation of other plugins
-
If you face problems with other plugins (i.e. during plugin installation/ activation) this may occur during handshake-procedures, or during maintenance of your plugin from the vendor. These procedures usually act like bots, as they pass a code or contents via certain automatically generated forms on your site.
In order to get this fixed you can either disable the option 🖥️ Apply on REST-API, or whitelist the IP address of your vendor, or you can whitelist the page which contains the maintenance form. In order to check whether such a problem occurs you can check the spam folder of this plugin. Here you find the site adress that you can use for whitelisting as «from_site» too
Generally, I recommend running the plugin in Explicit mode 🎯 as it’s more efficient and avoids such compatibility problems. Please refer to the «help» section for this option. -
Webhooks from Thrive automation don’t work properly when the plugin is activated
-
You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option 📄 Site-Whitelist. Do not forget to cut the protocoll (i.e. «http» and «https»).
Note: As Thrive doesn’t use the standard WordPress-REST-route, just deactivating the option 🖥️ Apply on REST-API will not work.
Generally, I recommend running the plugin in Explicit mode 🎯 as it’s more efficient and avoids those compatibility problems. Please refer to the «help» section for this option. -
Any Webhooks or API-calls do not work
-
You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option 📄 Site-Whitelist. Do not forget to cut the protocoll (i.e. «http» and «https»).
Alternatively you can deactivate the option 🖥️ Apply on REST-API if your services is using the standard WordPress-REST route.
Generally, I recommend running the plugin in Explicit mode 🎯 as it’s more efficient and avoids those compatibility problems. Please refer to the «help» section for this option. -
Problems with Borlabs Script Blocker
-
When you use the Borlabs Script Blocker to scan for JavaScripts, the scan doesn’t work properly, as it doesn’t show any JavaScripts. Just deactivate this plugin for the scan and activate it again after the scan.
-
No puedo corregir mis problemas
-
- Los mensajes importantes podrían mostrarse en la consola del navegador (F12) en la página problemática
- Siempre que publiques algo en el foro de ayuda, intenta facilitar todos los detalles
- Si el recaptcha no funciona en ningún formulario, avísame e intentaré corregirlo.
-
¿Cómo desactivar este plugin?
-
- Usa la página estándar de plugins de WordPress para desactivar y eliminar el plugin
- Al desactivar el plugin, se te preguntará el motivo. Si tienes algún problema, te agradecería que me lo informaras lo más detalladamente posible. Por lo general, los arreglaré rápidamente. Si me das detalles de contacto, puedo informarte tan pronto como se solucione.
Reseñas
Colaboradores y desarrolladores
«ReCaptcha compatible con el RGPD para todos los formularios y accesos.» es un software de código abierto. Las siguientes personas han colaborado con este plugin.
Colaboradores
«ReCaptcha compatible con el RGPD para todos los formularios y accesos.» ha sido traducido a 3 idiomas locales. Gracias a los traductores por sus contribuciones.
Traduce «ReCaptcha compatible con el RGPD para todos los formularios y accesos.» 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
3.5.7
- Warning for request method fixed
3.5.6
- Endless loading of Analytic box fixed
3.5.5
- Fixed: Spam-Check didin’t cover standard WOrdPress comments in explicit mode, as they are processed earlier than the spam check and the suvberglobals $_POST is emptied before. Thus wordpress-standard submissions are now always covered by the spam check. This holds now for «Explicit mode» too.
- Error messaging for identified spam standardized: The error message is now shown in all cases in the frontend, whenever spam is identified.
3.5.4
- CSS file for message page
3.5.3
- CSS was not loaded on message page
3.5.2
- Improved plugin-performance
- Whitelistings now can be filtered in «Explicit mode» too
3.5.1
- Option «Apply when logged in» removed for compatibility reasons. If you face problems with compatibility, please use the explicit mode
- Option «Excluded roles» removed for compatibility reasons. If you face problems with compatibility, please use the explicit mode
3.5
- Loading-Spinner for inboxes added
- Filter for Analytic Box added
- Usability for explicit mode improved
- Bug with nested fields for subject fields solved
3.4
- Critical fix of a database error
3.3
- Explicit mode enhanced
- Message patterns, now can be specified more precisely
- General recommendation to run on Explicit mode
3.2
- New mode «Analysis mode» to save all types of message in a new inbox «Analytic Box»
- New function to save message patterns, to enhance the scope of the spam protection. The message patterns can be saved from the respective messages in the «Analytic box»
- The whitelisting of ajax-action is now possible on all inboxes
- Visitor IPs can be saved (warning: If you enable this option, this is not compliant to GDPR)
- Bug fix: Passwords from fields with nested fieldnames (i.e. Elementor) where saved in clear with the messages. This issue is fixed now.
3.1
- Non-ajax-calls are only recognized if they stick to WP-standard for submissions
- Option added to modify the error message for identified spam
- Useful errormessage-format for wpDiscuz
3.0.8
- wordfence_syncAttackData-issue fixed
3.0.7
- Compatibility issues with divi fixed
- New function to whitelist submission-types directly from the spam-inbox
3.0.6
- Compatibility-issue with Wordfence fixed
- Better WooCommerce-suport
3.0.5
- Bug with wp-cron.php fixed
3.0.4
- Wordfence and other plugins backoffice-actions whitelisted
- Option for whitelisting ajax-calls enhanced with widlcard-capabilities
3.0.3
- WP-Cron whitelisted
3.0.2
- Submissions will now be saved for empty post-requests as well
3.0.1
- New options to delete messages after a certain period of time automatically
- New option to whitelist specific user roles from the processing when logged in
- Adjusted error message for Elementor Forms Pro
3.0
- Beware: If you update an existing release, test it. Some properties may be adjusted as the processing of post-requests has changed fundamentally and is alot more restrictive now. Absolutely every post-request will be considered from now on.
- If you are using wpforms and just flag spam, you have to change the flagging rules. Please see the respective hints for the option «Fieldname:prefix to flag spam»
- Whitelisting for ajax-requests added (called «actions» in the plugins properties-menü) + actions are saved with messages, such that they can be copied for whitelisting
- Explicit mode added: If this mode is activated the spam protection is only applied on explicitly listed ajax-actions. The processing of ordenary post-requests is not affected from that option
- Many performance improvements
- The plugin now directly catches all post-requests in the earliest phase of WordPress processing and exits the processing as soon as spam is identified. Therefore the server-capacity for spam-submissions is reduced by the plugin to the lowest possible minimum.
- Timestamp for message entries corrected
- Problems with application on interim-login fixed
- Bug with Site-Whitelisting fixed
2.5.2
- Deprecated usage of dynamic options replaced
- Deprecated Filter_Sanitize_String replaced
- Menu position warning fixed
2.5.1
- Option to filter WooCommerce shopping carts adjusted
2.5
- Added support for flagging messages for forminator and WPForms
- Added Whitelisting for sites
- Added option to disable/ enable REST API – support / may solve several compatibility issues with other plugins that do handshakes, or are maintained from the plugin vendor via REST API
- Added option to filter WooCommerce shopping carts from beeing saved
- Added a possibility to integrate this plugin into certain form builders via the new method spam_check( $fields )
2.4.1
- Dashboad-widget can be seen only by administrators now
- Support for WP forms added
- Warning-Bug solved
2.4
- Dashboard widged for the inbox added (has to be activated in the administration area)
- Style for the administration area renewed
- New option to disable/able the spam protection for logged-in users
- Support for Thrive Apprentice added
- Removed CF7 support-option, as CF7 is supported anyway
- Order auf messages in the inbox changed (now starting with the most current one)
2.3.3
- Bug with blocked entries solved
2.3.2
- Support for Forminator added
- Optimized namespaces in JavaScript for better plugin-compatibility
2.3.1
- Support for Thrive Architect / Thrive Automation added
2.3
- New feature to whitelist IPs, that shall be ignored and not beeing blocked from the plugin
- Errors with PHP version 5.6+ fixed
2.2.0
- Hash-puzzles are saved in the database right now
- Raised efficiency of the server-side spam-check
2.1.5
- Better resilience of the plugin
- Javascript know is directly echoed from PHP, to save loading time
2.1.4
- Special thanks to the user vptcnt
- Error 500 which appeard due to empty line reading in the stamp-log-file resolved
2.1
- Spam-check procedure optimized
2.0
- Complete code-rebuild
- Shopping carts and all other elements from Woocommerce are now working with the plugin
- Better integration of Elementor
- Popup-Bug for login-screen solved
- Plugin performance optimized
- The proof-of-work-check now happens before form submission via ajax. Thus collision with other plugins is minimized
1.4
- Elementor support added
1.3
- Problems with multiple forms on one page solved
- DOM-Integrity problem with non-unique IDs solved
1.2.1
Erroneous behaviour of the inbox with renamed WordPress-table-prefixes fixed
1.1.1
Empty JavaScript file deleted and not loaded anymore, to avoid loading the file uneccesary in the admin menu
1.1.0
Settings menu beautified
1.0
New: GDPR-compliant ReCaptcha for all forms has been released!