Ok. I've been using amemberPro for several years now. It's great. However, my most recent project requires me to branch out from the norm. And I'm having trouble figuring out the proper solution. Here's the nutshell version: I want each member to be able to have multiple subscriptions to the same product (I only have two) - Product 1 and Product 2. They can have as many subscriptions as they like to each. Product 1 is free, Product 2 is not. They're both recurring subscriptions. I've accomplished this by using the Renewal Group setting. I believe it's working fine. Members can add multiple subscriptions to each product from the member.php page. My problem is: I'm tracking the subscriptions in my application using the payment_id value - because I need a unique identifier not just an active subscription to a product. But when a recurring subscription expires (credit card is declined, etc.), I need the member to be able to renew that subscription without creating a new one. I need them to be able to renew it and simply update the current subscription without creating a new one (and thus a new payment_id). Maybe I'm missing the obvious - I hope so. Any help is appreciated.
Subscriptions Each payment_id is used to tie into a unique identifier (site id) for all the member's database information. They can have as many sites as they want (free or paid). For example: MemberID: 2 PaymentID: 3 - site 1 (unique id 3) PaymentID: 4 - site 2 (unique id 4) PaymentID: 5 - site 3 (unique id 5) So, if the payment_id is going to change upon renewal I've lost track of which site id the payment relates to. I'm using 2Checkout.com, Paypal and Free
Well, you can store site_id in payment record, right? Then when renewal will happen you can set the same site_id for new payment record (this can be done with a little code modification)
Modifications Yes, customization is always an option - but that makes upgrading more of a hassle. Ideally, I was hoping there was a way to set parameters to accomplish this. As far as modifying things, do you have some pointers as to how I should go about it? Every time a subscription is renewed (daily, monthly, etc.) it generates a new payment record (payment_id). So, how do I "pass the torch" each time the subscription is renewed? Is there a unique identifier anywhere that can tell me 'this payment is for this subscription'? Because we're dealing with multiple subscriptions of the same product too. Thanks much!
Constant 1. Is the receipt_id a constant -tied to a particular subscription? 2. Is the receipt_id a unique value?