New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Execute the following SQL-Commands in your Database:↵ DELETE FROM wp_options WHERE option_name = 'recaptcha_publickey';↵ DELETE FROM wp_options WHERE option_name = 'recaptcha_privatekey'; | You have to log in to add a translation. | Details | |
Original untranslated
Execute the following SQL-Commands in your Database:↵
DELETE FROM wp_options WHERE option_name = 'recaptcha_publickey';↵
DELETE FROM wp_options WHERE option_name = 'recaptcha_privatekey';
You have to log in to edit this translation. |
|||
| Add this line of Code somewhere at the end of your theme functions.php:↵ add_filter('wp_recaptcha_required','__return_false'); | You have to log in to add a translation. | Details | |
Original untranslated
Add this line of Code somewhere at the end of your theme functions.php:↵
add_filter('wp_recaptcha_required','__return_false');
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If lockout prevention is enabled you can simply delete the key set up a new one.↵ If not enter your domain name at "Domains" in a new line and wait up to 30 minutes. | You have to log in to add a translation. | Details | |
Original untranslated
If lockout prevention is enabled you can simply delete the key set up a new one.↵
If not enter your domain name at "Domains" in a new line and wait up to 30 minutes.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Find the part saying <code>data-sitekey="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"</code>↵ (The XXX-part should be your sitekey.) | You have to log in to add a translation. | Details | |
Original untranslated
Find the part saying <code>data-sitekey="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"</code>↵
(The XXX-part should be your sitekey.)
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You will either need one of the following:↵ - access to the settings for your sitekey on <a href="https://www.google.com/recaptcha/admin#list">reCaptcha API key administration</a>↵ - access to your WordPress installation (via SSH or FTP) or database access↵ - database access | You have to log in to add a translation. | Details | |
Original untranslated
You will either need one of the following:↵
- access to the settings for your sitekey on <a href="https://www.google.com/recaptcha/admin#list">reCaptcha API key administration</a>↵
- access to your WordPress installation (via SSH or FTP) or database access↵
- database access
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| When you see "Invalid domain for site key", then the key is okay in general, but not for↵ your domain. The server can not test this case, so an effective lockout prevention is not↵ possible. | You have to log in to add a translation. | Details | |
Original untranslated
When you see "Invalid domain for site key", then the key is okay in general, but not for↵
your domain. The server can not test this case, so an effective lockout prevention is not↵
possible.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If it says 'Invalid sitekey' and you checked the 'Prevent lockout' option on the plugin↵ settings (it's on by default) you can log in with an administrator account and ignore the↵ captcha. If the keys are really invalid, the plugin will let you in, so you can set up a↵ new keypair. | You have to log in to add a translation. | Details | |
Original untranslated
If it says 'Invalid sitekey' and you checked the 'Prevent lockout' option on the plugin↵
settings (it's on by default) you can log in with an administrator account and ignore the↵
captcha. If the keys are really invalid, the plugin will let you in, so you can set up a↵
new keypair.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Due to a lack of filters there is no (and as far as one can see, there will never be)↵ support for the <strong>MailPoet</strong> subscription form. | You have to log in to add a translation. | Details | |
Original untranslated
Due to a lack of filters there is no (and as far as one can see, there will never be)↵
support for the <strong>MailPoet</strong> subscription form.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| In <strong>WooCommerce</strong> the reset password form can not be protected by a captcha. Woocommerce does↵ not fire any action in the lost password form, so there is no way for the plugin to hook in.↵ Take a look at <a href="https://wordpress.org/support/topic/captcha-not-showing-on-lost-password-page?replies=7">this thread</a> for a workaround. | You have to log in to add a translation. | Details | |
Original untranslated
In <strong>WooCommerce</strong> the reset password form can not be protected by a captcha. Woocommerce does↵
not fire any action in the lost password form, so there is no way for the plugin to hook in.↵
Take a look at <a href="https://wordpress.org/support/topic/captcha-not-showing-on-lost-password-page?replies=7">this thread</a> for a workaround.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| As of version 4.3 CF7 comes with its own recaptcha. Both are supposed to work together.↵ I you want to keep the WP ReCaptcha functionality, e.g. if you want to hide the captcha↵ from known users, leave the integration in the CF7 settings unconfigured. | You have to log in to add a translation. | Details | |
Original untranslated
As of version 4.3 CF7 comes with its own recaptcha. Both are supposed to work together.↵
I you want to keep the WP ReCaptcha functionality, e.g. if you want to hide the captcha↵
from known users, leave the integration in the CF7 settings unconfigured.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| To handle this there is a filter <code>recaptcha_disabled_html</code>. You can return a message for your logged-in↵ users here. Check out the <a href="https://github.com/tareq1988/wp-recaptcha-integration">GitHub Repo</a> for details. | You have to log in to add a translation. | Details | |
Original untranslated
To handle this there is a filter <code>recaptcha_disabled_html</code>. You can return a message for your logged-in↵
users here. Check out the <a href="https://github.com/tareq1988/wp-recaptcha-integration">GitHub Repo</a> for details.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| On a <strong>Contact Form 7</strong> when the reCaptcha is disabled (e.g. for logged in users) the field↵ label will be still visible. This is due to CF7 Shortcode architecture, and can't be fixed. | You have to log in to add a translation. | Details | |
Original untranslated
On a <strong>Contact Form 7</strong> when the reCaptcha is disabled (e.g. for logged in users) the field↵
label will be still visible. This is due to CF7 Shortcode architecture, and can't be fixed.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A No Captcha definitely requires client side JavaScript enabled. That's how it does its↵ sophisticated bot detection magic. There is no fallback. If your visitor does not have↵ JS enabled the captcha test will not let him through. | You have to log in to add a translation. | Details | |
Original untranslated
A No Captcha definitely requires client side JavaScript enabled. That's how it does its↵
sophisticated bot detection magic. There is no fallback. If your visitor does not have↵
JS enabled the captcha test will not let him through.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| You can't have more than one old style reCaptcha on a page. This is a limitiation of↵ reCaptcha itself. If that's an issue for you, you should use the no Captcha Form. | You have to log in to add a translation. | Details | |
Original untranslated
You can't have more than one old style reCaptcha on a page. This is a limitiation of↵
reCaptcha itself. If that's an issue for you, you should use the no Captcha Form.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| With network activation entering the API key and setting up where a captcha is required↵ is up to the network admin. A blog admin can override the API key e.g. when his blog is↵ running under his/her own domain name. | You have to log in to add a translation. | Details | |
Original untranslated
With network activation entering the API key and setting up where a captcha is required↵
is up to the network admin. A blog admin can override the API key e.g. when his blog is↵
running under his/her own domain name.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Found in faq paragraph.