Data loss caused by PayPal subscription cancellation

[Cristián Lávaque]

Greg, I can perfectly understand what you're talking about! Thank you very much for reporting that unusual behavior. I'm forwarding the report to Jason so he inspects it ASAP and adds his comments here. Thank you for your patience.

[Jason Caldwell]

Investigating this now.
~ Thanks for your patience.

[Jason Caldwell]

Investigation completed.
Thanks for reporting this important issue.

What should happen: The user role remains exactly the same until the EOT for the fee that has already been paid. The user remains on the integrated MailChimp list as well. (I currently have s2Member set to process MailChimp list removals automatically as follows: "Anytime a User's Role changes ( including manual changes )" and "Anytime a User is deleted ( including manual deletions )".)

What does happen: The user role gets knocked back to 'Subscriber', their subscrib. ID gets erased, and they are deleted from the MailChimp list (as a side effect of their role having been incorrectly changed).

That's correct. This behavior is attributed to a recently discovered bug in s2Member v111105, resulting in this incorrect behavior in certain scenarios, which I suspect are affecting your installation as well.

This is being corrected for the next official release. Until then, there is a thread here where I've addressed this issue and we've been working to fully resolve it now for several days.

If you can't wait for the next release, there are patch files that can be used in the mean time ( i.e. until the next version is publicly available ).

Please apply the patches here:
viewtopic.php?f=4&t=14876&start=25#p53676
And also this additional patch, which was posted today:
viewtopic.php?f=4&t=14876&start=25#p54361

[Jason Caldwell]

You're very welcome.

Great -- many thanks, Jason! Will apply the fixes.

I'd read that thread before posting but thought it wouldn't apply to my own case, as I had never been running the earlier version mentioned there. (I.e., my installation started with v111105.) Assuming it's definitely the same problem, it looks like it can occur starting with v111105 after all.

Thanks again,
Greg

Yes, I'm sorry that I did not update that before. This latest patch corrects a bug that would affect all installations of s2Member, including the current release of s2Member v111105.