WordPress.org

Ready to get started?Download WordPress

Forums

Paid Memberships Pro
[resolved] PMP+ Stripe + Discount Code = Bugs (5 posts)

  1. paulhontz
    Member
    Posted 1 year ago #

    I just found a bug in Paid Membership Pro and discount codes. I'm using Stripe as my payment processor. Here is the problem:

    After I select what I want and enter my discount code, it will say "The discount code has been applied to your order." and "The price for membership is 0.00 now.".

    I'll then press "Submit and Checkout" and a javascript popup comes up and says "This card number looks invalid".

    Anyway around this?

    Technical Information:
    Paid Membership Pro Version 1.5.7
    Wordpress 3.5

    http://wordpress.org/extend/plugins/paid-memberships-pro/

  2. strangerstudios
    Member
    Plugin Author

    Posted 1 year ago #

    Sorry about this. Thanks for the heads up.

    This came up before, and I thought I had squashed this. What's happening is the membership level becomes free, so it hides the CC fields, but the submit button isn't being updated to skip the Stripe check.

    I will take a look when I get a chance this weekend.

    As a possible work around, if you pass the discount code in the web URL (../membership-checkout/?level=1&discount_code=free) it should apply the discount code before the form is generated and skip the Stripe check.

    Also, might be worth checking for javascript errors on your checkout page. It may give hints to what is going wrong, and maybe it's possible some other script is interfering with the PMPro JS code to disable the Stripe check.

  3. paulhontz
    Member
    Posted 1 year ago #

    Thanks for the speedy reply. I just opened up the page in Chrome with developer tools enabled and looked at the js console. I didn't have any errors relating to Stripe.

    Thanks again for your help and I'll be on the lookout for the fix.

  4. paulhontz
    Member
    Posted 1 year ago #

    Any update on this bug?

  5. paulhontz
    Member
    Posted 1 year ago #

    I can confirm that the new update fixes this problem. Thanks team!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic