UPDATE this morning fails – webpages affectred are blank!

Found conflict with plugin ‘Ninja Forms’ Version 3.2.1 and 3.2.2 by The WP Ninjas – workaround is to disable your plugin ‘WordPress ReCaptcha Integration’ Version 1.3.0 (when your plugin is enabled pages such as /wp-login.php and /wp-admin/ do not load, to login need to rename or delete plugin folder: /wp-content/plugins/wp-recaptcha-integration)

Same story for me.
That was because my forms were not converted to Ninja Forms 3 (option is in Forms / Settings / Advanced Settings) so the old class of Ninja Forms was used.
After conversion of the forms, it is working now, but some options like “don’t display for logged in users” don’t apply as the reCaptcha is the one from Ninja Forms (as far as I understand).

Ditto. Process of plugin elimination — i.e. renaming plugin folders — showed this one to be causing my wp-admin to be blank after attempting login. I actually was not yet on 1.3.0. Upgraded & activated. Same problem. Have not added, or removed, any plugins in probably a year, and all have been working well together to this point, so it would appear *this* is the culprit.

If you are using Ninja forms and you get an error like “NinjaForms()->get_settings() is not a valid function”, this might be because you are still using pre Ninja v3.0 forms.
I managed to have everything working by doing the following:
– disable reCaptcha plugin
– go to forms/setting/advanced setting and chose to upgrade to Ninja 3.0
– perform the upgrade (in my case the upgrade did not work… form was lost during upgrade…)
– then install and activate the latest reCaptcha plugin.

Note: if you are using reCaptcha only for Ninja forms, this is actually useless with the latest version as Ninja Forms 3.0 has its own reCaptcha. The latest reCaptcha plugin only gets or set eventually the settings of the reCaptcha key.

FYI: Don’t use Ninja. Never have. Still experience the problem.

I do, however, use Contact Form 7 (v4.9). Have noticed that occasionally some forms will have two captchas, probably for similar reasons. Disabling this plugin solved both issues.