I have many users with active recurring subscriptions using the paypal_r method which up until 3.1.8 worked well....I could be missing an option here, too, but have yet to find it. What used to occur is that when the subscription attempted to renew on it's cycle date but failed the status of the subscription would still be active and the period would still say "RECURRING". This worked well because these recurring subscriptions are set to attempt to renew 3 times if failing and on the final attempt will cancel. Upon the cancelling of 3 failed renews the status would change to expired and the user would lose access. What is occurring now is I think associated with one of the bullet points for changes made in this version; "Will now calculate expiration date automatically in aMember CP". On the renew date if it fails it is automatically going to the status of "expired" and the user loses access then even though there will be two more attempts. The period also is no longer "recurring" but set with an end date on the due date. This doesn't work well because the user has no recourse except to wait until it attempts to renew again which is 3 days for the 2nd attempt and if that fails another 5 days for the 3rd and final attempt. Basically, even though the subscription is past it's due date it is still not cancelled and the user becomes expired anyway where they should instead still have access at least until that 3rd and final attempt at a renew is made; how it worked until now, anyway. Is there something I'm missing here? Very possible I'm blind but have been up and down configuration options a few times now and nothing looks like it can be set to prevent the new behavior. thanks, Steve
I agree, and prefer the subscription extension method. Can you send in a tech support ticket to amember to have them change or at least make it an option- or if they do fix it for you, can you ask them to explain what they did so you can post it here? Thanks, David
sure...sent in and I'll post any resolution. Thanks for responding and letting me know this does appear to be beyond just my install of aMember
This is the response I got. : The reason why it changed makes sense to me.....I haven't seen the issue that is being referred to yet(at least that I'm aware of) and for customer sat will be editing that line. Haven't tested it yet but there ya go Steve
Yeah, the reasoning makes sense, I think if you stick with the now standard method, you may need to tell people that if their payment fails, they wont be able to access? It does make it better for incremental content. If on a 30 day payment schedule, and increment is set to 31, the failed user would get access the old way. Thanks for posting this- I'm sure others will find it useful. David