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
- The topic ‘Bug: billing_limit field in members and levels tables’ is closed to new replies.