Hello,

I just saw something weird. My user registration workflow is Allow registration: Yes and User Email Confirmation: Yes, before payment (override CB) under Plan workflows.

The client registered and then cancelled payment and the subscription. Then he finally decided that he wanted to buy the product and the subscription was activated as an upgrade. I'm getting all this info from the history log.

All sounds good, but the problem is that the SQL queries (from the SQL plugin) were not executed on this particular subscription. For all the other clients that registered and directly payed for their subscription these queries where executed. The only difference between both is that in the last case the subscriptions were activated as new.

Any advice please ?, this is important, since I rely on those queries upon subscription.

Thank you guys.

Queries only fire on activation and deactivation; not upgrade.

Hello krileon,

One of the problems here is that I don't know why the subscription was activated as an upgrade, since he hadn't any active nor inactive subscription within his account.

If you tell me that queries do not fire when upgrading, I understand, if and only if, he is upgrading from a previous active plan to a better one. However, even in this case, if the better plan needs to perform some additional queries or actions, this should be allowed.

I forgot to mention that I didn't receive the usual new user registration mail for this user upon activation of his account (after he payed). I looked up on my server logs and there is no trace of this mail, which means that it wasn't sent. I believe something is wrong here.

The questions are, why was this user's subscription considered as an upgrade ?, could you please explain to me what an activation/deactivation means, even an upgrade should be activated after payment is received and will be deactivated once its valid period is over.

What can I do in the meantime ?.

Thank you.

at any rate the SQL Actions plugin will be receiving an upgrade to handle plan upgrades, etc...

for next release perhaps ?, this is totally unexpected. For now I have to handle manually these upgrades, which is ...