Update Readme: #57

weDevsOfficial · Nov 30, 2015 · 16b7a7e · 16b7a7e
1 parent 3873810
commit 16b7a7e
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -19,9 +19,13 @@ Limitations
 
 - NoCaptcha only works with JavaScript enabled.
 
-- On a Contact Form 7 when the reCaptcha is disabled (e.g. for logged in users) the field
+- On a **Contact Form 7** 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 should also leave the Contact Form 7 internal recaptcha unconfigured (since CF7 4.3). 
+  CF7 will fall back to WP recaptcha then. Having both recaptchas configured will result in 
+  conflicts.
+
   To handle this there is a filter `recaptcha_disabled_html`. You can return a message for your logged-in 
   users here.
 

diff --git a/readme.txt b/readme.txt
@@ -63,6 +63,10 @@ running under his/her own domain name.
   To handle this there is a filter `recaptcha_disabled_html`. You can return a message for your logged-in 
   users here. Check out the [GitHub Repo](https://github.com/mcguffin/wp-recaptcha-integration) for details.
 
+- Please leave the **Contact Form 7** internal recaptcha unconfigured. Don't enter any 
+  keys under Contact / integration. 
+  CF7 will fall back to the WP Recaptcha. Two recaptchas together will not work.
+
 - Old style reCaptcha does not work together with **WooCommerce**. 
 
 - In **WooCommerce** the reset password form can not be protected by a captcha. Woocommerce does