New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Anti-spam, Spam protection, ReCaptcha for all forms and GDPR-compliant | Anti-spam, Spam protection, ReCaptcha for all forms and GDPR-compliant | Details |
Original current
Anti-spam, Spam protection, ReCaptcha for all forms and GDPR-compliant
You have to log in to edit this translation. |
|||
| ↑ | Anti-spam - CAPTCHA that protects all forms against spam and brute-force. Invisible and GDPR-compliant. | Anti-spam - Un CAPTCHA que protege todos los formularios contra el spam y la fuerza bruta. Invisible y conforme a RGPD. | Details |
Original current
Anti-spam - CAPTCHA that protects all forms against spam and brute-force. Invisible and GDPR-compliant.
CommentShort description. You have to log in to edit this translation. |
|||
| Elementor Pro Forms, Contact Form 7, Fluent Forms, Jetpack Forms, Divi Forms, WPForms, Forminator, Thrive Architect & Thrive Apprentice, Gravity Forms, Formidable Forms, Mailchimp for WordPress Forms, BuddyPress Registration Form, bbPress Create Topic & Reply Forms, Ultimate Member Forms, wpDiscuz Custom Comments Form, Easy Digital Downloads Forms, Paid Memberships Pro Forms, MemberPress Forms, WP-Members Forms, WP User Frontend Forms, CheckoutWC & Flux Checkout, Ninja Forms, Everest Forms, Formidable Forms, WS Forms, Quform, Otter Blocks, Typeform, NEX-Forms, Bit Form, Form Maker, Funnelforms, Mailjet, Jotform, Page Builder, Metform, Calculated Fields Form, JetFormBuilder, weForms, Responsive Contact Form Builder, Zoho Forms, Smart Forms, Kali Forms, Happyforms, ApplyOnline, Subscribe Forms, FormCraft, Advanced Forms, CRM Perks Forms, Tripetto, Formstack, BuddyForms, vcita, Easy Form Builder, SimpleForm | Elementor Pro Forms, Contact Form 7, Fluent Forms, Jetpack Forms, Divi Forms, WPForms, Forminator, Thrive Architect & Thrive Apprentice, Gravity Forms, Formidable Forms, Mailchimp for WordPress Forms, BuddyPress Registration Form, bbPress Create Topic & Reply Forms, Ultimate Member Forms, wpDiscuz Custom Comments Form, Easy Digital Downloads Forms, Paid Memberships Pro Forms, MemberPress Forms, WP-Members Forms, WP User Frontend Forms, CheckoutWC & Flux Checkout, Ninja Forms, Everest Forms, Formidable Forms, WS Forms, Quform, Otter Blocks, Typeform, NEX-Forms, Bit Form, Form Maker, Funnelforms, Mailjet, Jotform, Page Builder, Metform, Calculated Fields Form, JetFormBuilder, weForms, Responsive Contact Form Builder, Zoho Forms, Smart Forms, Kali Forms, Happyforms, ApplyOnline, Subscribe Forms, FormCraft, Advanced Forms, CRM Perks Forms, Tripetto, Formstack, BuddyForms, vcita, Easy Form Builder, SimpleForm | Details | |
Original current
Elementor Pro Forms, Contact Form 7, Fluent Forms, Jetpack Forms, Divi Forms, WPForms, Forminator, Thrive Architect & Thrive Apprentice, Gravity Forms, Formidable Forms, Mailchimp for WordPress Forms, BuddyPress Registration Form, bbPress Create Topic & Reply Forms, Ultimate Member Forms, wpDiscuz Custom Comments Form, Easy Digital Downloads Forms, Paid Memberships Pro Forms, MemberPress Forms, WP-Members Forms, WP User Frontend Forms, CheckoutWC & Flux Checkout, Ninja Forms, Everest Forms, Formidable Forms, WS Forms, Quform, Otter Blocks, Typeform, NEX-Forms, Bit Form, Form Maker, Funnelforms, Mailjet, Jotform, Page Builder, Metform, Calculated Fields Form, JetFormBuilder, weForms, Responsive Contact Form Builder, Zoho Forms, Smart Forms, Kali Forms, Happyforms, ApplyOnline, Subscribe Forms, FormCraft, Advanced Forms, CRM Perks Forms, Tripetto, Formstack, BuddyForms, vcita, Easy Form Builder, SimpleForm
CommentFound in description list item. You have to log in to edit this translation. |
|||
| If the message doesn't appear here, or is already in scope, please give me a note↵ In general I recommend to run the plugin in the <strong>Explicit mode 🎯</strong> and to do so with all types of submissions that you which to be considered for the spam check. | Si el mensaje no aparece aquí o ya está en el alcance, por favor, hazme saber. En general, recomiendo ejecutar el plugin en el <strong>modo explícito 🎯</strong> y hacerlo con todos los tipos de envíos que desees que se consideren para la verificación de spam. | Details | |
Original current
If the message doesn't appear here, or is already in scope, please give me a note↵
In general I recommend to run the plugin in the <strong>Explicit mode 🎯</strong> and to do so with all types of submissions that you which to be considered for the spam check.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Open the message and enhance the scope of the spam to this type of message | Abre el mensaje y amplía el alcance del spam a este tipo de mensaje. | Details | |
Original current
Open the message and enhance the scope of the spam to this type of message
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Submit the form and look for the message that has been saved for the new submission in the <strong>Analytic Box</strong> | Envía el formulario y busca el mensaje que se ha guardado para la nueva presentación en la <strong>Caja de Análisis</strong>. | Details | |
Original current
Submit the form and look for the message that has been saved for the new submission in the <strong>Analytic Box</strong>
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Activate the <strong>Analysis mode 🔍</strong>, | Activa el <strong>modo de análisis 🔍</strong>, | Details | |
Original current
Activate the <strong>Analysis mode 🔍</strong>,
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| [vimeo https://player.vimeo.com/video/905897718] | [vimeo https://player.vimeo.com/video/905897718] | Details | |
Original current
[vimeo https://player.vimeo.com/video/905897718]
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Setup Guide | Guía de configuración | Details | |
Original current |
|||
| 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. | Cuando utilices el Borlabs Script Blocker para buscar JavaScripts, la exploración puede no funcionar correctamente, ya que no muestra ningún JavaScript. Desactiva este plugin para la exploración y vuelve a activarlo después de la exploración. | Details | |
Original current
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option <strong>📄 Site-Whitelist</strong>. Do not forget to cut the protocoll (i.e. "http" and "https").↵ Alternatively you can deactivate the option <strong>🖥️ Apply on REST-API</strong> if your services is using the standard WordPress-REST route.↵ Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option. | Necesitas incluir en la lista blanca los webhooks respectivos (aquellos que el servicio respectivo está utilizando para llamar a tu sitio) con la opción <strong>📄 Lista blanca del sitio</strong>. No olvides eliminar el protocolo (es decir, "http" y "https"). Como alternativa, puedes desactivar la opción <strong>🖥️ Aplicar en REST-API</strong> si tu servicio está utilizando la ruta estándar de WordPress-REST. En general, recomiendo ejecutar el plugin en <strong>Modo explícito 🎯</strong> ya que es más eficiente y evita problemas de compatibilidad. Consulta la sección "ayuda" para obtener información sobre esta opción. | Details | |
Original current
You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option <strong>📄 Site-Whitelist</strong>. Do not forget to cut the protocoll (i.e. "http" and "https").↵
Alternatively you can deactivate the option <strong>🖥️ Apply on REST-API</strong> if your services is using the standard WordPress-REST route.↵
Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option <strong>📄 Site-Whitelist</strong>. 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 <strong>🖥️ Apply on REST-API</strong> will not work.↵ Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option. | Necesitas incluir en la lista blanca los webhooks respectivos (aquellos que el servicio respectivo está utilizando para llamar a tu sitio) con la opción <strong>📄 Lista blanca del sitio</strong>. No olvides eliminar el protocolo (es decir, "http" y "https"). Nota: Como Thrive no utiliza la ruta estándar de WordPress-REST, simplemente desactivar la opción <strong>🖥️ Aplicar en REST-API</strong> no funcionará. En general, recomiendo ejecutar el plugin en <strong>Modo explícito 🎯</strong>, ya que es más eficiente y evita problemas de compatibilidad. Consulta la sección de "ayuda" para obtener información sobre esta opción. | Details | |
Original current
You need to whitelist the respective webhooks ( those which the respective service is using to call your site) with the option <strong>📄 Site-Whitelist</strong>. 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 <strong>🖥️ Apply on REST-API</strong> will not work.↵
Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids those compatibility problems. Please refer to the "help" section for this option.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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 <strong>🖥️ Apply on REST-API</strong>, 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 <strong>Explicit mode 🎯</strong> as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option. | Si te enfrentas a problemas con otros plugins (por ejemplo, durante la instalación/activación del plugin), esto puede ocurrir durante procedimientos de handshake o durante el mantenimiento de tu plugin por parte del proveedor. Estos procedimientos generalmente actúan como bots, ya que pasan un código o contenido a través de ciertos formularios generados automáticamente en tu sitio. Para solucionar esto, puedes desactivar la opción <strong>🖥️ Aplicar en REST-API</strong>, o incluir en la lista blanca la dirección IP de tu proveedor, o puedes incluir en la lista blanca la página que contiene el formulario de mantenimiento. Para verificar si ocurre un problema de este tipo, puedes revisar la carpeta de spam de este plugin. Aquí encontrarás la dirección del sitio que puedes usar para la lista blanca como "from_site" también. En general, recomiendo ejecutar el plugin en <strong>Modo explícito 🎯</strong>, ya que es más eficiente y evita problemas de compatibilidad. Consulta la sección de "ayuda" para obtener información sobre esta opción. | Details | |
Original current
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 <strong>🖥️ Apply on REST-API</strong>, 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 <strong>Explicit mode 🎯</strong> as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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 <strong>🖥️ Apply on REST-API</strong>, 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 <strong>📄 Site-Whitelist</strong> 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 <strong>Explicit mode 🎯</strong> as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option. | Si encuentras problemas con la activación de Jetpack, esto puede ocurrir durante el procedimiento de handshake de Jetpack. Este procedimiento actúa como un bot cuando pasa una contraseña desde una dirección IP específica a un formulario generado automáticamente en tu sitio. Para solucionar esto, debes desactivar la opción <strong>🖥️ Aplicar en REST-API</strong> o incluir en la lista blanca el formulario respectivo que se utiliza para intercambiar la contraseña. Generalmente, necesitas seguir estos pasos para incluir en la lista blanca: Revisa la carpeta de spam en busca del mensaje respectivo que ha sido bloqueado. Copia la dirección del sitio "from_site". Pega la dirección del sitio en la opción <strong>📄 Lista blanca del sitio</strong> en la configuración del sitio. Presiona guardar. Normalmente, necesitas incluir en la lista blanca dos sitios diferentes para conectar Jetpack: Para conectar el sitio: tu-domnio-sin-protocolo/?rest_route=/jetpack/v4/verify_registration/ Para conectar tu usuario: tu-domnio-sin-protocolo/?rest_route=/jetpack/v4/remote_authorize/ En general, recomiendo ejecutar el plugin en <strong>Modo explícito 🎯</strong> ya que es más eficiente y evita problemas de compatibilidad. Consulta la sección de "ayuda" para obtener información sobre esta opción. | Details | |
Original current
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 <strong>🖥️ Apply on REST-API</strong>, 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 <strong>📄 Site-Whitelist</strong> 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 <strong>Explicit mode 🎯</strong> as it's more efficient and avoids such compatibility problems. Please refer to the "help" section for this option.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids compatibility problems. Please refer to the "help" section for this option. | En general, recomiendo ejecutar el plugin en <strong>Modo explícito 🎯</strong>, ya que es más eficiente y evita problemas de compatibilidad. Consulta la sección de "ayuda" para obtener información sobre esta opción. | Details | |
Original current
Generally, I recommend running the plugin in <strong>Explicit mode 🎯</strong> as it's more efficient and avoids compatibility problems. Please refer to the "help" section for this option.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
Export as
Comment
Plugin name.