Version 1.8.13.3 of Paid Memberships Pro is out with a single bug fix. If you were using Stripe as your primary gateway and also offer a second gateway option (via our Add PayPal Express addon, our Pay by Check addon, or other custom code) the checkout form failed to submit when the secondary gateway was chosen. If you are using this kind of configuration, you should update immediately or risk losing sales.

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 1.8.13.3 specifically here.


Comments (10)

I’m using the WP Courseware – Paid Memberships Pro Add On and it has stopped sending out emails to my students after updating Paid Memberships Pro.

I will try the email trouble shooting. I am using Version 1.8.13.3. It was working up until recently, that is why I was thinking it was something in this update that may be affecting it. Not only is it not sending the email, but when I tested it by registering and paying for a level it showed my new membership in the user section as not having any membership level, even though it took the right amount of money for that level from my bank account. Really weird.

I just tried it again. I registered for a paid level and it took the money, but in the user section under level it says “none”. No emails are sent out and I am not being assigned the level I am paying for. Scratching my head here.

We use a hidden “fullname” field at checkout as a “honeypot” to catch spammers. If you enter anything into this field (like automatic spam bots will), the checkout will fail with that error. Maybe your theme or some code is making that field visible? Maybe your browser’s autocomplete is filling that field out?

how Do i fix this. How to hide full name. The autofill form are not in our control on others computer however to fix that. Because even if I use the plugin on twenty17 theme it shows the same field in checkout.

Most autofill systems ignore the hidden fields. The fields are hidden with this CSS here and work on my sites using the 2017 theme.

https://github.com/strangerstudios/paid-memberships-pro/blob/dev/css/frontend.css#L335-L337

Something on your specific setup must be interfering with that. If you share a link to your site, we might be able to see what is causing the issue. Please use the wp.org forums if you won’t pay for member support. Support through blog comments is hard.

https://wordpress.org/support/plugin/paid-memberships-pro

Leave a Reply

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