I got response from PayPal IPN, one of the user cancel the Auto Renewal Payment. Response is just perfect in the log file. But S2Member plugin didn’t remove that user account from WordPress.
Please help me how to solve this issue.
S2Member is not removing account from WP Users if user skipped the EOT Payment
Just to be perfectly clear: is the User past the EOT date + the grace period?
Yes @JediShark
User past the EOT date. What is this Grace Period?
I got email from the PayPal. Here is the snap shot
Actually user skipped the payment at the EOT time. 13th of March and user still in the Paid members and have all the ability of paid members. It should removed from the users list. Right? But its still there
The default grace period is 24 hours (86400 seconds) so, yes, it looks to me like s2Member should have demoted them. If you have logging enabled, which you shouldn’t on a production site, check the paypal-ipn log for any errors. If you don’t have logging enabled, you’ll need to enable logging and run some tests to see if the EOT IPN communication is working.
I already done that @JediShark. I check in the Logging, Every thing is just fine, PayPal EOT IPN communication is working perfectly. There is no error in the paypal-ipn log. Website is on the Media Temple. In the Past I got some errors that S2Member was not updating the transactions on WP. In log file I got response from PayPal IPN but S2Member was not updating the payments like last payment date, new date etc. So I disabled the Media Temple Database and other caches and my problem was resolved. But now this is happening. In log files I got response from PayPal IPN that user skipped the payment, but user still in the paid members list. S2Member should demoted that user.
If you’ve previously had problems with the database not being updated and resolved them by disabling the database caching, I’d try that now. It most likely will not fix this particular problem, so you need to demote/delete this User manually. Then conduct a couple of test transactions (short subscription term and a low transaction amount) and see if the problem is resolved.
If there is a problem with the caching you might want to report that on GitHub.
If disabling the caches does not fix the issue, I’d suggest testing in a clean WordPress installation. The WordPress machine has many “moving parts” and tracking down problems is not always easy.