Version 2.0.5 of Paid Memberships Pro is out with a handful of bug fixes and new features to better counteract checkout spam. Read on to explore the full details of the update and steps you need to take to utilize these new features.

Please update Paid Memberships Pro from the plugins page of your WordPress dashboard. You can also get the latest version of PMPro here or version 2.0.5 specifically here.

New Feature: reCAPTCHA v3

This version includes a new option for the reCAPTCHA setting. If reCAPTCHA is enabled, you will be able to choose between the v2 and v3 implementations of reCAPTCHA. The v2 setting is the same version from previous versions of Paid Memberships Pro. The v3 setting uses the reCAPTCHA API v3 and also uses the ‘invisible reCAPTCHA’. This hides the additional checkbox that users were previously required to complete. A reCAPTCHA icon will sometimes show up in the bottom right of the screen.

If you are using the v3 reCAPTCHA option, we now check the reCAPTCHA before submitting the form as well as during the form processing. This is meant to keep spammers from using your checkout form to test credit cards with gateways like Stripe.

We recently encountered a situation where spammers were testing thousands of credit cards on our checkout form every hour. Oddly, the “Stripe v2” API doesn’t detect this kind of activity (they just think your site is super busy). Stripe could suspend your account due to the spam. The reCAPTCHA v3 setup should prevent this kind of abuse. We are working on adding support for the Stripe v3 Elements API which has PCI compliance benefits in addition to avoiding this kind of checkout spam. The Stripe v3 Elements update should be ready by the end of the summer.

We encourage all users, especially Stripe and Braintree users to use the reCAPTCHA v3 option for paid and free levels. Even if you are using reCAPTCHA v2, we encourage you to create a new set of license keys for v3 and use those. To do so:

  1. Create an account at the reCAPTCHA site.
  2. Go to the reCAPTCHA admin console.
  3. Click + to create a new site.
  4. Choose the v3 option.
  5. Add your domain.
  6. Note the Site Key and Secret Key.
  7. Visit Memberships -> Settings -> Advanced Settings in your WordPress dashboard.
  8. For the “Use reCAPTCHA?” setting choose “Yes – All Memberships”.
  9. Choose the reCAPTCHA v3 option.
  10. Enter the Site Key and Secret Key.
  11. Click the Save Settings button.
  12. IMPORTANT: Test your checkout to make sure there are no issues.

The full list of updates is below.

  • BUG FIX: Fixed fatal error on return from 2Checkout.
  • BUG FIX: Removed error when installing PMPro via WP-CLI.
  • BUG FIX: Fix database upgrade error on localhost environment. (Thanks, codezz on GitHub)
  • BUG FIX: Fixed issue where the credit card expiring email didn’t include user info because the user ID wasn’t passed in properly. (Thanks, David Cervantes Caballero)
  • BUG FIX: Fixed typo on edit level page. (Thanks, Theuns Coetzee)
  • BUG FIX: Fixed bug with daily revenue reports not showing up in some cases.
  • BUG FIX: Now checking before cancelling a Stripe subscription at the gateway to see if it has already been cancelled.
  • BUG FIX/ENHANCEMENT: Now caching the query results in pmpro_getMembershipLevelsForUser(). This improves performance, especially when there are many posts on one page to check membership for. (Thanks, Seagyn Davis)
  • BUG FIX/ENHANCEMENT: Now sending display_name to the $data array passed to PMPro email filters. (Thanks, David Cervantes Caballero)
  • BUG FIX/ENHANCEMENT: Now searching for the last order with “success” or “pending” status on the Billing page.
  • BUG FIX/ENHANCEMENT: Added pmpro_checkout_preheader_before_get_level_at_checkout and pmpro_checkout_preheader_after_get_level_at_checkout action hooks. Using pmpro_checkout_preheader_before_get_level_at_checkout to start the session earlier now.
  • BUG FIX/ENHANCEMENT: Removed the membership_code_id and membership_code as field options for the member shortcode. These weren’t working and it’s unclear what would be meant to ask for a user’s discount code since a user could have several orders with or without discount codes. Added “membership_description” and “membership_confirmation” instead.
  • BUG FIX/ENHANCEMENT: Filtering the password reset message to make sure the link still works in all cases when we convert emails to HTML.
  • REFACTOR: Now running the pmpro_billing_preheader hook after the jquery.creditCardValidator script is enqueued in preheader/billing.php to match how we do it in preheader/checkout.php. (Thanks, Rafe Colton)
Tagged . Bookmark the . Last updated: . Titled

Comments (21)

I have the same problem when using v3 of reCAPTCHA.
“reCAPTCHA failed. (missing-input) Please try again”?

Is there a solution for this? Create already 2 support tickets for this.

Hello, thank you for reaching out on this article. I see one of our support staff replied to your reCAPTCHA support ticket on 22 April. Debugging can be complicated and frustrating and is often a slow process of elimination or to achieve replicating the issue consistently. Please follow up with our team in the Support topic so that we can give you the hands-on help you need.

I have the same issue. It seems to be linked to having a need for both the email and password to be entered twice for verification, The Paid Membership Pro Register short code only has a single entry (at least it does on my Aardvark theme).

It will not pass unless those fields 2 extra fields have been completed. It does bounce you back to another default version where both can be entered but unfortunately the user experience is not good.

I assume this will be addressed in the next update. We will wait and see.

If I have activated reCAPTCHA v3 and entered the keys for a different plugin (contactform7). Do I also need to update my PMPro advanced settings and enter the keys again?

Received notice from Stripe that we need to be PCI compliant with Stripe.js V3 by June 7th or fill out the 56 page self assessment. Noticed that you are estimating end of summer for the Stripe.js V3 update. How realistic is this update timeline? Any possibility it will be out sooner? Very concerned we won’t have enough time to either fill out this form or update the V3 before the Stripe deadline.

I updated PMPro on my site to the newest version 2.0.5 and now suddenly all of my paid members are locked out and don’t have access.

All of the settings were unchanged as well as the levels associated with the content. All users that are “subscribers” have been locked out and their respective membership levels NOT allowing access despite being active paid members.

Only users who are “administrators” have access to the content now.

This is a HUGE problem. I need help ASAP OR some way of reverting back to the previous version that was working properly.

There are no changes in this release that lead me to believe this would occur and no other sites are reporting it.

Were any other updates made at the time of this change? Are the members all still in the list under Memberships > Members in the admin dashboard?

You can download zip files of previous versions here:

Or try this WP Rollback plugin:

Lots of things happen when WP updates that could cause issues like this. If you figure out what specifically is causing your members to be locked out, let us know. You can also post to our member support to get help from our staff on working through this with you.

Hi to all from Italy:-)))
I just revolutionized my site by uninstalling memberpress and using your awesome plugin. One thing, however, is very frustrating. I do not have the possibility to make the visitor who clicks on a page (or a protected post) redirected on another specific page with all the registration tables (which was instead foreseen on Memberpress). In practice, in options panel, you have only entered the possibility of leaving a message, there is no alternative option to redirect the user to a specific page instantly. I think it’s a pretty serious lack for such a complete plugin! Thank you!

Hi Kimberly, thanks for reply (well, it could be useful if you could add to post a mail notify for new replies:-))))
Your solution could be the answer I’m searching for but unfortunately… it is a premium add-on! :-(((((

What would cause this error which has appeared sometimes on our checkout: “reCAPTCHA failed. (missing-input) Please try again”?

We are using v3 of reCAPTCHA.

That sounds like the error that comes up when the API call to reCAPTCHA is missing some input. Double check that you have the correct key and secret set on the settings. Check that when reCAPTCHA needs to ask you about cars or street signs that that screen isn’t hidden or covered up on your site. It’s actually really hard to force reCAPTCHA to test you to test that, but look into it if you can.

Open a ticket in our support forums so we can get some more information and access to your site to test this. Thanks.

Thanks. I will open a ticket.
I haven’t been able to reproduce the problem myself but the site’s owner does get the error. That makes troubleshooting tricky so I was kind of hoping for a known bug.

Hey, sorry about that. This is a common type of issue that we try to avoid. I will pass this on to the WP Courseware team (I think we have access to the repos too) to make sure it doesn’t happen.

Hi Jason. I updated to this version yesterday and now I am getting this error in my dashboard: WP Courseware – Paid Memberships Pro addon: The Paid Memberships Pro plugin has not been detected. Is it installed and activated?

The whole site is broken now.

Thank you for the new update. I have a question:
Is it possible to move reCAPTCHA Badge from the right to the left?
Thank you

Leave a Reply

For faster support related to issues on your specific site please open a ticket in our members support area.

Your email address will not be published. Required fields are marked *