Paypal and cancel subscription

[Anton Shevchuk]

Hi,
Now i tested last version (2.9.4) of s2member plugin and found trouble with cancel subscription, my steps:

register user with "one day subscription" (s2member-level-1)
cancel subscription by paypal

Result after one day: user leave s2member-level-1

Logs:

Code: Select all

array (
  'transaction_subject' => '',
  'txn_type' => 'subscr_payment',
  'subscr_id' => 'I-YPRY9XRDMFXX',
  's2member_log' =>
  array (
    0 => 's2Member POST vars verified through a POST back to PayPal®.',
    1 => 's2Member originating domain ( _SERVER[HTTP_HOST] ) validated.',
    2 => 's2Member txn_type identified as subscr_payment.',
  ),
  'ccaps' => NULL,
  'level' => '1',
)

array (
  'txn_type' => 'subscr_signup',
  'subscr_id' => 'I-YPRY9XRDMFXX',
  's2member_log' =>
  array (
    0 => 's2Member POST vars verified through a POST back to PayPal®.',
    1 => 's2Member originating domain ( _SERVER[HTTP_HOST] ) validated.',
    2 => 's2Member txn_type identified as (web_accept|subscr_signup).',
    3 => 's2Member txn_type identified as (web_accept|subscr_signup) w/o update vars.',
    4 => 'Signup Confirmation Email sent to Customer, with a URL to assist w/ registration.',
  ),
  'ccaps' => NULL,
  'level' => '1',
)

// 08:40:29 May 14, 2010 PDT
array (
  'txn_type' => 'subscr_cancel',
  'subscr_id' => 'I-YPRY9XRDMFEN',
  's2member_log' =>
  array (
    0 => 's2Member POST vars verified through a POST back to PayPal®.',
    1 => 's2Member originating domain ( _SERVER[HTTP_HOST] ) validated.',
    2 => 'Properly ignoring this IPN request. The txn_type does not require any action on the part of s2Member.',
  ),
)


Thank you for great job.

[rossagrant]

If you mean that even after you cancelled the subscription that the user still has the level one access then that is because you have a new style PayPal account.

You can tell that you have a new account as your user subscribe ID starts above with the letter I.

In their stupidity Paypal have removed the 'End Of Transaction' IPN from being sent on new accounts so unless you manually demote the member then they will never be demoted.

Many people including myself are in this position and can't use S2Member until either Paypal reinstate this function or Jason can find a way around it.

Jason is currently looking into the best way around this.
I'm sure he'll let us know any day what he has worked out.

[Jason Caldwell]

Great questions. ( Thanks Ross ).
We spent a great deal of time on this issue, so that future versions of s2Member would not be adversely affected by this policy change at PayPal®. s2Member v3.0+ works around the "new PayPal® account"/subscr_eot issue gracefully.

You can read the full Changelog for s2Member 3.0 here:
viewtopic.php?f=4&t=97

# EOT bug fix & improvements. ( 2010 PayPal® accounts ). EOT = End Of Term. s2Member has been updated to support newer PayPal® accounts ( those opened after Oct 15th, 2009 ). Newer PayPal® accounts do NOT send an IPN/`subscr_eot` in all cases. This has been reported to PayPal® by several developers. At any rate, s2Member can deal with this gracefully now, by keeping a record of payments/periods/changes, and monitoring other signals sent by PayPal®. This allows s2Member to take control of the situation, at the appropriate time, using s2Member's built-in Auto-EOT System ( new ).

The communication from PayPal® -> s2Member is seamless ( once again ); even in PayPal® accounts created after October 15th, 2009. These changes will NOT negatively effect existing installations of s2Member. If anything, it will improve your experience. More importantly, if your PayPal® account was established in 2010, you will definitely want to upgrade to s2Member v3.0+.