Showing EOT for users from old version of plugin

[foliovision]

Hello,

we need to display EOT for our users on the site. The site has 2010 s2Member Level 1 users and 2013 users in total.

Currently only 7 users have the s2member_auto_eot_time field set. I understand that this field is populated with buy-now transactions only: http://www.primothemes.com/forums/viewtopic.php?f=4&t=6403&hilit=eot#p14735

There is also s2member_last_payment_time field (http://www.primothemes.com/forums/viewtopic.php?f=4&t=6196&start=25#p13849), but only 111 users have that. Also, only 119 users have s2member_paid_registration_times.

This is probably because we ugraded to version s2Member 110710 only 2 weeks ago. Before, the site was using version 2.0. So it looks like it was not recording these fields. So:

1. Was version 2.0 of s2Member recording 's2member_last_payment_time' and 's2member_paid_registration_times'?

2. I can see users which registered more than 1 year ago and their profiles are still "s2Member Level 1". Because we upgraded to 110710 version only recently, these users don't have any of s2member_last_payment_time or s2member_paid_registration_times fields. The "Automatic EOT Behavior" is set to "Demote (convert them to Free Subscribers)". Was this also working in the older version 2.0? Or did they renewed their accounts in the meantime, but they did it befoure our upgrade to 110710, so there is no record of that in the plugin?

3. We need to figure this out. Without s2member_last_payment_time or s2member_paid_registration_times I can't tell the EOT for the user. I can only assume, that if the user was registered in April 2009, and it's still listed as "s2Member Level 1", he had to renew his account in April 2011 (so it wasn't recorded by the plugin, because we upgraded to 110710 in July) and it's valid until April 2012 (we have only yearly subscriptions).

Would that work? This depends on my question 2 - was old s2Member 2.0 processing EOT? Give us a hint here please, we could also check out our logs of PayPal transactions.

Thanks,
Martin

[Jason Caldwell]

Thanks for bringing this thread to my attention.
Hi Martin. You mentioned that you *were* using s2Memer v2.0. Was that s2Member v2.0 on the dot?, or what was the exact version? I can tell you that s2Member v2.x did NOT set any of these data fields, as it relied completely on PayPal IPN communication at that point. That's why I ask, because I'm a little puzzled as to how some of your members have those data fields, when none of those were set in s2Member v2.x.

[foliovision]

Hello Jason,

the site used 2.0 until few weeks ago. Here is the plugin header:

Version: 2.0
Stable tag: 2.0
Framework: P-1.6
Tested up to: 2.8.6
Requires at least: 2.8.4
Requires: WordPress® 2.8.4+, PHP 5.2+
WordPress MU Compatible: yes

Now the site uses 110710:

Version: 110710
Stable tag: 110710
Framework: WS-P-110523

So that's why some of the latest users have these fields filled in.

Please let me know what you think about my idea in number 3.

Thanks,
Martin

[Jason Caldwell]

Thanks for clarifying that.

3. We need to figure this out. Without s2member_last_payment_time or s2member_paid_registration_times I can't tell the EOT for the user. I can only assume, that if the user was registered in April 2009, and it's still listed as "s2Member Level 1", he had to renew his account in April 2011 (so it wasn't recorded by the plugin, because we upgraded to 110710 in July) and it's valid until April 2012 (we have only yearly subscriptions).

Would that work? This depends on my question 2 - was old s2Member 2.0 processing EOT? Give us a hint here please, we could also check out our logs of PayPal transactions.

Well, the only way you'll know with 100% certainty, is to look each of them up inside your PayPal account, matching the Paid Subscr. ID that s2Member recorded, against the current state of the "Subscription" inside your PayPal account. That being said, your logic sounds fine to me. If all of your paid Members are on a 1 year subscription, and they've not been expired yet, that would indicate to me that recurring charges have remained successful ( i.e. nothing was cancelled or expired ). In that case, you would take the Member's registration time, and work out when the next payment should be due, based on a yearly cycle.

Even back in s2Member v2.0, we still DID process EOTs. It's just that s2Member v2.0 relied solely on IPN communication, whereas current versions of s2Member record other specifics ( i.e. variouos payment times ) in order to workaround some potential conflicts that exist in PayPal's handling of EOTs. In all cases, even in s2Member v2.x, if PayPal notified s2Member of a cancellation or expiration, s2Member would have knocked them back down to Level #0, or deleted them completely, based on your EOT configuration.