WordPress ReCaptcha Integration - Version 1.2.3

Version Description

Download this release

Release Info

Developer podpirate
Plugin Icon 128x128 WordPress ReCaptcha Integration
Version 1.2.3
Comparing to
See all releases

Code changes from version 1.2.2 to 1.2.3

Files changed (3) hide show
  1. languages/wp-recaptcha-integration.pot +11 -9
  2. readme.txt +79 -123
  3. wp-recaptcha-integration.php +46 -24
languages/wp-recaptcha-integration.pot CHANGED
@@ -1,21 +1,21 @@
1
  # Copyright (C) 2020 Jörn Lund
2
- # This file is distributed under the same license as the WP reCaptcha Integration plugin.
3
  msgid ""
4
  msgstr ""
5
- "Project-Id-Version: WP reCaptcha Integration 1.2.2\n"
6
  "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-recaptcha-integration\n"
7
  "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
8
  "Language-Team: LANGUAGE <LL@li.org>\n"
9
  "MIME-Version: 1.0\n"
10
  "Content-Type: text/plain; charset=UTF-8\n"
11
  "Content-Transfer-Encoding: 8bit\n"
12
- "POT-Creation-Date: 2020-03-09T10:12:47+00:00\n"
13
  "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
14
  "X-Generator: WP-CLI 2.4.0\n"
15
  "X-Domain: wp-recaptcha-integration\n"
16
 
17
  #. Plugin Name of the plugin
18
- msgid "WP reCaptcha Integration"
19
  msgstr ""
20
 
21
  #. Plugin URI of the plugin
@@ -23,7 +23,7 @@ msgid "https://wordpress.org/plugins/wp-recaptcha-integration/"
23
  msgstr ""
24
 
25
  #. Description of the plugin
26
- msgid "<strong>PLUGIN ABANDONED!</strong> Integrate reCaptcha in your blog. Supports no Captcha (new style recaptcha). Provides of the box integration for signup, login, comment forms and lost password."
27
  msgstr ""
28
 
29
  #. Author of the plugin
@@ -326,10 +326,12 @@ msgstr ""
326
  msgid "Get an image CAPTCHA"
327
  msgstr ""
328
 
329
- #: wp-recaptcha-integration.php:67
330
- msgid "Warning:"
 
331
  msgstr ""
332
 
333
- #: wp-recaptcha-integration.php:68
334
- msgid "“WP reCaptcha Integration” is no longer maintained. It may disappear without further notice."
 
335
  msgstr ""
1
  # Copyright (C) 2020 Jörn Lund
2
+ # This file is distributed under the same license as the ABANDONED WP reCaptcha Integration plugin.
3
  msgid ""
4
  msgstr ""
5
+ "Project-Id-Version: ABANDONED WP reCaptcha Integration 1.2.3\n"
6
  "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-recaptcha-integration\n"
7
  "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
8
  "Language-Team: LANGUAGE <LL@li.org>\n"
9
  "MIME-Version: 1.0\n"
10
  "Content-Type: text/plain; charset=UTF-8\n"
11
  "Content-Transfer-Encoding: 8bit\n"
12
+ "POT-Creation-Date: 2020-05-12T16:14:12+00:00\n"
13
  "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
14
  "X-Generator: WP-CLI 2.4.0\n"
15
  "X-Domain: wp-recaptcha-integration\n"
16
 
17
  #. Plugin Name of the plugin
18
+ msgid "ABANDONED WP reCaptcha Integration"
19
  msgstr ""
20
 
21
  #. Plugin URI of the plugin
23
  msgstr ""
24
 
25
  #. Description of the plugin
26
+ msgid "Integrate reCaptcha in your blog. Supports no Captcha (new style recaptcha). Provides of the box integration for signup, login, comment forms and lost password."
27
  msgstr ""
28
 
29
  #. Author of the plugin
326
  msgid "Get an image CAPTCHA"
327
  msgstr ""
328
 
329
+ #: wp-recaptcha-integration.php:66
330
+ #: wp-recaptcha-integration.php:76
331
+ msgid "WP Recaptcha Integration is no longer maintained."
332
  msgstr ""
333
 
334
+ #: wp-recaptcha-integration.php:67
335
+ #: wp-recaptcha-integration.php:78
336
+ msgid "It will likely vanish from the WordPress plugin repository by September 2020."
337
  msgstr ""
readme.txt CHANGED
@@ -1,25 +1,29 @@
1
- === WordPress ReCaptcha Integration ===
2
  Contributors: podpirate
3
- Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=F8NKC6TCASUXE
4
  Tags: security, captcha, recaptcha, no captcha, login, signup, contact form 7, ninja forms, woocommerce
5
  Requires at least: 3.8
6
- Tested up to: 4.8
7
- Stable tag: 1.2.2
 
8
  License: GPLv2 or later
9
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
10
 
11
- reCaptcha for login, signup, comment forms, Ninja Forms and woocommerce.
12
 
13
  == Description ==
14
 
15
- Integrate reCaptcha in your blog. Supports no Captcha as well as old style recaptcha.
16
- Provides of the box integration for signup, login, comment formsand Ninja Forms as well
 
 
 
17
  as a plugin API for your own integrations.
18
 
19
- = Features: =
20
- - Secures login, signup und comments with a recaptcha.
21
- - Supports old as well as new reCaptcha.
22
- - Works together with
23
  - WP Multisite
24
  - bbPress (thanks to [Tareq Hasan](http://tareq.wedevs.com/)
25
  - BuddyPress
@@ -40,62 +44,82 @@ Latest Files on GitHub: [https://github.com/mcguffin/wp-recaptcha-integration](h
40
 
41
  = Compatibility =
42
 
43
- On a **WP Multisite** you can either activate the plugin network wide or on a single site.
44
 
45
- Activated on a single site everything works as usual.
46
 
47
- With network activation entering the API key and setting up where a captcha is required
48
- is up to the network admin. A blog admin can override the API key e.g. when his blog is
49
  running under his/her own domain name.
50
 
51
 
52
  = Known Limitations =
53
- - You can't have more than one old style reCaptcha on a page. This is a limitiation of
54
- reCaptcha itself. If that's an issue for you, you should use the no Captcha Form.
55
 
56
- - A No Captcha definitely requires client side JavaScript enabled. That's how it does its
57
- sophisticated bot detection magic. There is no fallback. If your visitor does not have
58
- JS enabled the captcha test will not let him through.
59
 
60
- - On a **Contact Form 7** when the reCaptcha is disabled (e.g. for logged in users) the field
61
- label will be still visible. This is due to CF7 Shortcode architecture, and can't be fixed.
62
 
63
- To handle this there is a filter `recaptcha_disabled_html`. You can return a message for your logged-in
64
  users here. Check out the [GitHub Repo](https://github.com/mcguffin/wp-recaptcha-integration) for details.
65
 
66
- - As of version 4.3 CF7 comes with its own recaptcha. Both are supposed to work together.
67
- I you want to keep the WP ReCaptcha functionality, e.g. if you want to hide the captcha
68
- from known users, leave the integration in the CF7 settings unconfigured.
69
 
70
- - Old style reCaptcha does not work together with **WooCommerce**.
71
 
72
- - In **WooCommerce** the reset password form can not be protected by a captcha. Woocommerce does
73
- not fire any action in the lost password form, so there is no way for the plugin to hook in.
74
  Take a look at [this thread](https://wordpress.org/support/topic/captcha-not-showing-on-lost-password-page?replies=7) for a workaround.
75
 
76
- - Due to a lack of filters there is no (and as far as one can see, there will never be)
77
  support for the **MailPoet** subscription form.
78
 
79
  == Installation ==
80
 
81
- First follow the standard [WordPress plugin installation procedere](http://codex.wordpress.org/Managing_Plugins).
82
-
83
- Then go to the [Google Recaptcha Site](http://www.google.com/recaptcha), register your site and enter your API-Keys on the configuration page.
84
 
85
  == Frequently asked questions ==
86
 
87
- = The login captcha says 'ERROR: (something somthing)'. What can I do? =
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
88
 
89
- If it says 'Invalid sitekey' and you checked the 'Prevent lockout' option on the plugin
90
- settings (it's on by default) you can log in with an administrator account and ignore the
91
- captcha. If the keys are really invalid, the plugin will let you in, so you can set up a
 
 
 
 
92
  new keypair.
93
 
94
- When you see "Invalid domain for site key", then the key is okay in general, but not for
95
- your domain. The server can not test this case, so an effective lockout prevention is not
96
  possible.
97
 
98
- You will either need one of the following:
99
  - access to the settings for your sitekey on [reCaptcha API key administration](https://www.google.com/recaptcha/admin#list)
100
  - access to your WordPress installation (via SSH or FTP) or database access
101
  - database access
@@ -128,7 +152,7 @@ You will either need one of the following:
128
  3. Remove the line above from your theme functions.php.
129
 
130
 
131
- **If you have Database access**
132
 
133
  1. Execute the following SQL-Commands in your Database:
134
  <code>DELETE FROM wp_options WHERE option_name = 'recaptcha_publickey';</code>
@@ -136,26 +160,19 @@ You will either need one of the following:
136
 
137
  (Please note that `wp_options` might have a different prefix in your installation.)
138
 
139
- 2. After the login you will see a message asking you to set up the API keys.
140
 
141
  3. Set up a new keypair on Google and test it.
142
 
143
 
144
- **If none of these works for you**
145
-
146
- That's too bad...
147
-
148
-
149
- = I can't get it to work with my custom comments form. Will you fix for me? =
150
-
151
- Nope. I cannot give support on your individual projects for free, no matter how many one
152
- star reviews you will give me. Have a look at the project wiki or find a WordPress coder.
153
 
 
154
 
155
- = Privacy: Will the captcha send the visitors IP address to google? =
156
 
157
  Yes and no. The captcha verification process, comming into effect after the user has solved
158
- the challenge does not require the disclosure of the visitors IP address, so it is omitted.
159
 
160
  But everything related to the displaying of the captcha widget like the challenge image,
161
  the JavaScripts and so on is loaded directly from Google and is very likely to be logged,
@@ -165,17 +182,6 @@ In other words: Google knows which (recaptcha protected) website is accessed fro
165
 
166
  If that's an issue for you, you better use a self hosted solution.
167
 
168
-
169
- = Will you support plugin XYZ? =
170
-
171
- If XYZ stands for a widely used free and OpenSource plugin in active development with some
172
- 100k+ downloads I will give it a try. Just ask.
173
-
174
- If XYZ is some rarely used plugin (about 1k+ active installs or so), I will accept pull
175
- requests on github and push it to the WP repository. Please note that in such cases I will
176
- not feel responsible for code maintainance.
177
-
178
-
179
  = The captcha does not show up. What’s wrong? =
180
 
181
  On the plugin settings page check out if the option “Disable for known users” is activated (it is by default).
@@ -196,58 +202,6 @@ Here is some code that will fix it:
196
  If the problem still persist, Houston really has a problem, and you are welcome to post a support request.
197
 
198
 
199
- = Disabled submit buttons should be grey! Why aren't they? =
200
-
201
- Very likely the Author of your Theme didn't care that a non functinal form element should
202
- look different than a functional one. This how you can overcome that issue:
203
-
204
- - Go to (https://gist.github.com/mcguffin/7cbfb0dab73eb32cb4a2)
205
- - Click the "Download Gist" button
206
- - Unpack the `.tar.gz` file.
207
- - Create a zip Archive out of the included file `grey-out-disabled.php` and name it `grey-out-disabled.zip`.
208
- - Install and activate it like any other WordPress plugin
209
-
210
-
211
- = I want my visitors to solve only one Captcha and then never again. Is that possible? =
212
-
213
- Yes. You can store in a session if a captcha was solved, and use the `wp_recaptcha_required`
214
- filter to supress further captchas. See (https://github.com/mcguffin/wp-recaptcha-integration#real-world-example)
215
- for a code example.
216
-
217
-
218
- = I found a bug. Where should I post it? =
219
-
220
- I personally prefer GitHub but you can post it in the forum as well. The plugin code is here: [GitHub](https://github.com/mcguffin/wp-recaptcha-integration)
221
-
222
-
223
- = I want to use the latest files. How can I do this? =
224
-
225
- Use the GitHub Repo rather than the WordPress Plugin. Do as follows:
226
-
227
- 1. If you haven't already done: [Install git](https://help.github.com/articles/set-up-git)
228
-
229
- 2. in the console cd into Your 'wp-content/plugins´ directory
230
-
231
- 3. type `git clone git@github.com:mcguffin/wp-recaptcha-integration.git`
232
-
233
- 4. If you want to update to the latest files (be careful, might be untested with your WP-Version) type `git pull.
234
-
235
- Please note that the GitHub repository is more likely to contain unstable and untested code. Urgent fixes
236
- concerning stability or security (like crashes, vulnerabilities and alike) are more likely to be fixed in
237
- the official WP plugin repository first.
238
-
239
-
240
- = I found a bug and fixed it. How can I contribute? =
241
-
242
- Either post it on [GitHub](https://github.com/mcguffin/wp-recaptcha-integration) or—if you are working on a forked repository—send me a pull request.
243
-
244
-
245
- = Will you accept translations? =
246
-
247
- Since late 2015 WordPress.org offers a plugin translation API. Just use the
248
- "Translate this plugin" button in the right sidebar.
249
-
250
-
251
  == Screenshots ==
252
 
253
  1. Plugin Settings (v 1.1.4)
@@ -257,13 +211,11 @@ Since late 2015 WordPress.org offers a plugin translation API. Just use the
257
 
258
  == Changelog ==
259
 
260
- = 1.2.2 =
261
- - End-of-Life!
262
-
263
- = 1.2.1 =
264
- - Drop most of Contact form 7 and Ninja Forms support. (Both have their own recaptcha now)
265
- - Register Form compatibility with WooCommerce 3.0+ Thanks to [ywatt](https://github.com/ingomarent) and [MrFent37](https://wordpress.org/support/users/mrfent37/)
266
- - Fix WSOD
267
 
268
  = 1.2.0 =
269
  - Support [cformsII](https://wordpress.org/plugins/cforms2/) (thanks to [Bastian Germann](https://github.com/bgermann))
@@ -401,3 +353,7 @@ Initial Release
401
  The plugin offers some filters to allow themes and other plugins to hook in.
402
 
403
  See [GitHub-Repo](https://github.com/mcguffin/wp-recaptcha-integration) for details.
 
 
 
 
1
+ === ABANDONED WordPress ReCaptcha Integration ===
2
  Contributors: podpirate
3
+ Donate link: https://noyb.eu/en/support-us
4
  Tags: security, captcha, recaptcha, no captcha, login, signup, contact form 7, ninja forms, woocommerce
5
  Requires at least: 3.8
6
+ Tested up to: 4.9
7
+ Stable tag: 1.2.3
8
+ Requires PHP: 5.4
9
  License: GPLv2 or later
10
  License URI: http://www.gnu.org/licenses/gpl-2.0.html
11
 
12
+ *ABANDONED* reCaptcha for login, signup, comment forms, Ninja Forms and woocommerce.
13
 
14
  == Description ==
15
 
16
+ **This plugin is no longer maintained.** It will likely vanish from the WordPress plugin repository by September 2020.
17
+ Thanks to everyone who contributed or used it.
18
+
19
+ Used to integrate reCaptcha in your blog. Supported no Captcha as well as old style recaptcha.
20
+ Provided of the box integration for signup, login, comment forms and Ninja Forms as well
21
  as a plugin API for your own integrations.
22
 
23
+ = The Features were: =
24
+ - Secure login, signup und comments with a recaptcha.
25
+ - Supported old as well as new reCaptcha.
26
+ - Worked together with
27
  - WP Multisite
28
  - bbPress (thanks to [Tareq Hasan](http://tareq.wedevs.com/)
29
  - BuddyPress
44
 
45
  = Compatibility =
46
 
47
+ On a **WP Multisite** you could either activate the plugin network wide or on a single site.
48
 
49
+ Activated on a single site everything worked as usual.
50
 
51
+ With network activation entering the API key and setting up where a captcha was required
52
+ was up to the network admin. A blog admin could override the API key e.g. when his blog is
53
  running under his/her own domain name.
54
 
55
 
56
  = Known Limitations =
57
+ - You couldn't have more than one old style reCaptcha on a page. This was a limitiation of
58
+ reCaptcha itself. If that was an issue for you, you should have used the no Captcha Form.
59
 
60
+ - A No Captcha definitely required client side JavaScript enabled. That was how it did its
61
+ sophisticated bot detection magic. There have been no fallbacks. If your visitor hadn't
62
+ JS enabled the captcha test was not letting him through.
63
 
64
+ - On a **Contact Form 7** when the reCaptcha was disabled (e.g. for logged in users) the field
65
+ label has been be still visible. This was due to CF7 Shortcode architecture, and couldn't be fixed.
66
 
67
+ To handle this there was a filter `recaptcha_disabled_html`. You could return a message for your logged-in
68
  users here. Check out the [GitHub Repo](https://github.com/mcguffin/wp-recaptcha-integration) for details.
69
 
70
+ - As of version 4.3 CF7 came with its own recaptcha. Both were supposed to work together.
71
+ I you want to keep the WP ReCaptcha functionality, e.g. if you wanted to hide the captcha
72
+ from known users, you could leave the integration in the CF7 settings unconfigured.
73
 
74
+ - Old style reCaptcha did not work together with **WooCommerce**.
75
 
76
+ - In **WooCommerce** the reset password form could not be protected by a captcha. Woocommerce did
77
+ not fire any action in the lost password form, so there was no way for the plugin to hook in.
78
  Take a look at [this thread](https://wordpress.org/support/topic/captcha-not-showing-on-lost-password-page?replies=7) for a workaround.
79
 
80
+ - Due to a lack of filters there was no (and as far as one could see, there will never would have been)
81
  support for the **MailPoet** subscription form.
82
 
83
  == Installation ==
84
 
85
+ As th edevelpoment of plugin has stopped quite some time ago, you really should not install it.
 
 
86
 
87
  == Frequently asked questions ==
88
 
89
+ = Why did you abandon the plugin? =
90
+
91
+ **The short answer:** Privacy concerns.
92
+
93
+ **The long answer:** Googles (and others) business model is to record as much as
94
+ possible of your behaviour and to turn it into a model of your future behaviour
95
+ in order to sell it to who ever is willing to pay for it. every little bit you do
96
+ on the internet is a small stroke in the big picture which is showing you – your
97
+ fears and desires, your likes and dislikes, your days and nights – you name it.
98
+
99
+ As long as you only see some tailor-made ads, you may think this is not be a big
100
+ problem. In risk assessment it may become one. In politics it definetly is. In
101
+ 2020 we see personality profiles being used in dubious political campaigns,
102
+ asymmetric warfare and as a suppression technique in numerous dictatorships.
103
+ Your benevolent despot from the future knows what comes next...
104
+
105
+ Like hydrogen bombs personality profiles generated from behavioural data should
106
+ not exists in the first place. The least I can do as a developer, is to not help
107
+ collecting it.
108
 
109
+ Thanks for reading that far.
110
+
111
+ = The login captcha sayed 'ERROR: (something somthing)'. What could I do? =
112
+
113
+ If it sayed 'Invalid sitekey' and you checked the 'Prevent lockout' option on the plugin
114
+ settings (it's on by default) you could log in with an administrator account and ignore the
115
+ captcha. If the keys were really invalid, the plugin would have been letting you in, so you could set up a
116
  new keypair.
117
 
118
+ When you've seen "Invalid domain for site key", then the key was okay in general, but not for
119
+ your domain. The server could not test this case, so an effective lockout prevention was not
120
  possible.
121
 
122
+ You would either needed one of the following:
123
  - access to the settings for your sitekey on [reCaptcha API key administration](https://www.google.com/recaptcha/admin#list)
124
  - access to your WordPress installation (via SSH or FTP) or database access
125
  - database access
152
  3. Remove the line above from your theme functions.php.
153
 
154
 
155
+ **If you had Database access**
156
 
157
  1. Execute the following SQL-Commands in your Database:
158
  <code>DELETE FROM wp_options WHERE option_name = 'recaptcha_publickey';</code>
160
 
161
  (Please note that `wp_options` might have a different prefix in your installation.)
162
 
163
+ 2. After the login you would have seen a message asking you to set up the API keys.
164
 
165
  3. Set up a new keypair on Google and test it.
166
 
167
 
168
+ **If none of these worked for you**
 
 
 
 
 
 
 
 
169
 
170
+ That was too bad...
171
 
172
+ = Privacy: Did the captcha send the visitors IP address to google? =
173
 
174
  Yes and no. The captcha verification process, comming into effect after the user has solved
175
+ the challenge does not require the disclosure of the visitors IP address, so it was omitted.
176
 
177
  But everything related to the displaying of the captcha widget like the challenge image,
178
  the JavaScripts and so on is loaded directly from Google and is very likely to be logged,
182
 
183
  If that's an issue for you, you better use a self hosted solution.
184
 
 
 
 
 
 
 
 
 
 
 
 
185
  = The captcha does not show up. What’s wrong? =
186
 
187
  On the plugin settings page check out if the option “Disable for known users” is activated (it is by default).
202
  If the problem still persist, Houston really has a problem, and you are welcome to post a support request.
203
 
204
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
205
  == Screenshots ==
206
 
207
  1. Plugin Settings (v 1.1.4)
211
 
212
  == Changelog ==
213
 
214
+ = 1.3.0 =
215
+ - Drop support for legacy recaptcha
216
+ - Drop support for WP < 4.2
217
+ - Fix: WooCommerce checkout Error (thanks to [ywatt](https://github.com/ywatt))
218
+ - Fix: Textdomain loading (Thanks, [Bajoras](https://github.com/Bajoras) for bringing this to my attetnion)
 
 
219
 
220
  = 1.2.0 =
221
  - Support [cformsII](https://wordpress.org/plugins/cforms2/) (thanks to [Bastian Germann](https://github.com/bgermann))
353
  The plugin offers some filters to allow themes and other plugins to hook in.
354
 
355
  See [GitHub-Repo](https://github.com/mcguffin/wp-recaptcha-integration) for details.
356
+
357
+ == Upgrade notice ==
358
+
359
+ Version 1.3.2 only brings a deprecation notice to the wp admin.
wp-recaptcha-integration.php CHANGED
@@ -1,12 +1,13 @@
1
  <?php
2
  /*
3
- Plugin Name: WP reCaptcha Integration
4
  Plugin URI: https://wordpress.org/plugins/wp-recaptcha-integration/
5
- Description: <strong>PLUGIN ABANDONED!</strong> Integrate reCaptcha in your blog. Supports no Captcha (new style recaptcha). Provides of the box integration for signup, login, comment forms and lost password.
6
- Version: 1.2.2
7
  Author: Jörn Lund
8
  Author URI: https://github.com/mcguffin/
9
  Text Domain: wp-recaptcha-integration
 
10
  */
11
 
12
  /* Copyright 2014 Jörn Lund (email : joern AT podpirate DOT org)
@@ -25,6 +26,10 @@ Text Domain: wp-recaptcha-integration
25
  Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
26
  */
27
 
 
 
 
 
28
  /**
29
  * Autoload Classes
30
  *
@@ -50,30 +55,47 @@ function wp_recaptcha_disable_updates($value) {
50
  }
51
  add_filter('site_transient_update_plugins', 'wp_recaptcha_disable_updates');
52
 
53
- WP_reCaptcha::instance();
54
-
55
-
56
- function wp_recaptcha_deprecation_notice() {
57
- /*
58
- '<tr class="plugin-update-tr%s" id="%s" data-slug="%s" data-plugin="%s">' .
 
 
 
 
 
 
59
 
60
- */
61
  ?>
62
- <tr class="plugin-update-tr active" >
63
- <td class="plugin-update colspanchange" colspan="3" style="position:relative;top:-1px;">
64
- <div class="notice notice-error notice-alt inline">
65
- <p>
66
- <span class="dashicons dashicons-warning"></span>
67
- <strong><?php esc_html_e('Warning:','wp-recaptcha-integration'); ?></strong>
68
- <?php esc_html_e('“WP reCaptcha Integration” is no longer maintained. It may disappear without further notice.','wp-recaptcha-integration'); ?>
69
- </p>
70
- </div>
71
- </td>
72
- </tr>
 
 
 
 
 
 
 
73
  <?php
74
  }
75
 
76
- if ( is_admin() ) {
77
- add_action('after_plugin_row_wp-recaptcha-integration/wp-recaptcha-integration.php','wp_recaptcha_deprecation_notice');
 
 
 
 
 
78
  WP_reCaptcha_Options::instance();
79
- }
1
  <?php
2
  /*
3
+ Plugin Name: ABANDONED WP reCaptcha Integration
4
  Plugin URI: https://wordpress.org/plugins/wp-recaptcha-integration/
5
+ Description: Integrate reCaptcha in your blog. Supports no Captcha (new style recaptcha). Provides of the box integration for signup, login, comment forms and lost password.
6
+ Version: 1.2.3
7
  Author: Jörn Lund
8
  Author URI: https://github.com/mcguffin/
9
  Text Domain: wp-recaptcha-integration
10
+ Domain Path: /languages
11
  */
12
 
13
  /* Copyright 2014 Jörn Lund (email : joern AT podpirate DOT org)
26
  Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
27
  */
28
 
29
+
30
+ define( 'WP_RECAPTCHA_INTEGRATION_FILE', __FILE__ );
31
+ define( 'WP_RECAPTCHA_INTEGRATION_DIRECTORY', plugin_dir_path(__FILE__) );
32
+
33
  /**
34
  * Autoload Classes
35
  *
55
  }
56
  add_filter('site_transient_update_plugins', 'wp_recaptcha_disable_updates');
57
 
58
+ function wp_recaptcha_deprecation_plugin_row( $file, $plugin_data ) {
59
+
60
+ $wp_list_table = _get_list_table( 'WP_Plugins_List_Table' );
61
+ printf(
62
+ '<tr class="plugin-update-tr active" id="wp-recaptcha-integration" data-slug="wp-recaptcha-integration" data-plugin="wp-recaptcha-integration/wp-recaptcha-integration.php">' .
63
+ '<td colspan="%1$d" class="plugin-update colspanchange">' .
64
+ '<div class="update-message notice inline error notice-alt"><p><strong>%2$s</strong> %3$s</p></div></td></tr>',
65
+ esc_attr( $wp_list_table->get_column_count() ),
66
+ esc_html__( 'WP Recaptcha Integration is no longer maintained.', 'wp-recaptcha-integration' ),
67
+ esc_html__( 'It will likely vanish from the WordPress plugin repository by September 2020.', 'wp-recaptcha-integration' )
68
+ );
69
+ }
70
 
71
+ function wp_recaptcha_deprecation_admin_notice() {
72
  ?>
73
+ <div class="notice notice-error">
74
+ <p>
75
+ <strong>
76
+ <?php esc_html_e( 'WP Recaptcha Integration is no longer maintained.', 'wp-recaptcha-integration' ); ?>
77
+ </strong>
78
+ <?php esc_html_e( 'It will likely vanish from the WordPress plugin repository by September 2020.', 'wp-recaptcha-integration' ); ?>
79
+ <?php
80
+ global $pagenow;
81
+ if ( 'plugins.php' !== $pagenow && current_user_can('install_plugins') ) {
82
+ printf(
83
+ '<a href="%s">%s</a>',
84
+ admin_url('plugins.php'),
85
+ esc_html__( 'Disable it on the plugins page' )
86
+ );
87
+ }
88
+ ?>
89
+ </p>
90
+ </div>
91
  <?php
92
  }
93
 
94
+ add_action( 'after_plugin_row_wp-recaptcha-integration/wp-recaptcha-integration.php', 'wp_recaptcha_deprecation_plugin_row', 10, 2 );
95
+ add_action( 'admin_notices', 'wp_recaptcha_deprecation_admin_notice' );
96
+
97
+ WP_reCaptcha::instance();
98
+
99
+
100
+ if ( is_admin() )
101
  WP_reCaptcha_Options::instance();