I have created several test subscription orders which I purposely stopped the order. The subscription validity times for these are over a week past today. Yet none of the accounts have expired....I am looking at the rule "Update subscription expiration schedule" and it checks to see if the validity is changed or not equal to an unchanged user account validity field....but the validity field is not empty it has a date of over a week ago....What am I missing here....I have found the flowchart for version 1.1 but it appears this part of it is different.

Shouldn't it check to see if the validity is past the current date and not if it is empty?

Comments

markusa’s picture

Or maybe the rule "End subscription when validity is unset"....this checks to see if the validity is empty....should we not be checking to see if the validity is set to before now? When is the validity set to empty? And is this only done when the user profile is updated? So if the user never updates his profile then these rules are never triggered?

How is the subscription triggered to end....the only place I see it is the Component "Subscription End" which has a rule "Clear subscription settings" that is supposed to empty the validity field.

But unless I'm missing something "Subscription end" is only triggered when the validity is already set to empty.

A little clarification on the flow of subscription expiration would be greatly appreciated.

markusa’s picture

Ahh it all works well. When the user cancels the subscription created in their paypal account commerce_sp_paypal receives a notification and sets the skip expiration field to unchecked...this user update pops up an rule responding to "update of profile". Then the rules scheduler takes over. Great module. Thanks

mrconnerton’s picture

Status: Active » Closed (works as designed)

Helping clean issue queue