Version 1.7.15.2 of Paid Memberships Pro is out with a handful of bug fixes affecting some Stripe and Payflow users.

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

The full list of updates is below.

  • BUG: Stripe JS looks for a field with id AND name = CardType now so the new checkout code is compatible with older checkout templates and will avoid “complete all fields” errors.
  • BUG: Removed the urlencode wrappers on the Payflow API calls. Payflow seems to expect the values to be NOT encoded.
  • BUG: No longer running email content through wpautop if there is already HTML in an included header or footer for the email. (Thanks, Erik Bertrand)

Comments (16)

The Import Users From CSV plugin can only import so many members at one time. On shared hosting, it might be as low as 50 members at a time. Even on dedicated servers, it can sometimes only do 200-400. So try to split up your CSV files.

Hi Jason,
Does PMPro allow for the purchase of multiple membership “products/levels” in a single financial transaction?
If not, would it be possible via Woocommerce and the Subscriptions extension?

I just posted about this:
https://www.paidmembershipspro.com/2015/02/multiple-membership-levels-per-user-pmpro-workarounds/

With WooCommerce, you could technically checkout for more than one PRODUCT, but you would only be able to have one PMPro membership level at a time. (So which ever level was added last would probably be the one given to the user rather than them both.) However that link above has some work arounds that might work for you.

Hey Jason, your plugin is being reported as not up to date for WordPress release 4.1. I would like to use your Paid Pro version on a new website but want to make sure it is compatible with what I am using. You may want to upload the new file with the patch for Stripe and the other gateways at the same time. Just and FYI. Good Work.

It’s working for me on the dev version. I probably just need to update the readme in the repository or have more people click on the compatible button there. There isn’t any reason it wouldn’t work with 4.1 though.

I was trying to test a dummy card payment with pmpro using visa for sandbox testing and its giving me this error “Internal Error”

Which gateway? Which test card number? Make sure you are following their sandbox rules. Also, try again since sometimes there are real unknown “internal errors” on the sandbox sites. In particular I run into issues with PayPal’s sandbox about once a month or so and just have to wait a couple hours for them to fix things.

Leave a Reply

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