Support » Plugin: Paid Memberships Pro - Content Restriction, User Registration, & Paid Subscriptions » Bug: billing_limit field in members and levels tables

  • PMPro 1.7.6.

    Setting a recurring billing_limit in the admin section causes the billing_limit field in the levels table to be set as expected, i.e. 5 as a billing limit.

    However when a new user subscribes, the billing_limit field in their entry in the user table is also set to 5. Is this intended? Otherwise it appears to be a bug as then recurring payments are never taken.

    Surely, how it should work is that the billing_limit is set in the levels table, then in the users table, the billing_limit should initially be set to 1. Then the following should happen:

    if member.billing_limit <= levels.billing_limit:
    take payment;
    member.billing_limit++;
    else:
    do nothing. billing_limit reached.

    If this is not a bug, then where is the field that should be incremented so that billings can be tested against the billing_limit in levels table?

    Regards,
    Alex

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jason Coleman

    (@strangerstudios)

    Hi Alex,

    The billing_limit field set in the pmpro_memberships_users table is just the initial value. It is not used to control the payments after checkout. It’s actually the gateway (PayPal, Stripe, etc) which controls how many payments to run before stopping the subscriptions. (The billing limit value is passed to the gateway at checkout, creating a subscription their.)

    Also note that after 5 subscription payments, the membership will remain active unless you also add an expiration date. The expiration date is controlled on the WP/PMPro side.

    Hope this clears things up.

    Thread Starter Alex Biddle

    (@alex-biddle)

    Thanks for your reply.

    It did clear things up thank you. I have been implementing a cron “subscription” that used a simple card payment taken through PMPro and cancels it after a period of time.

    In the end, I used a custom variable in the WordPress metadata to act as the billing_limit.

    Possibly my extension for PMPro to create its own “subscriptions” could be a future feature.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Bug: billing_limit field in members and levels tables’ is closed to new replies.