Community Support Forums

I'm having a problem where PayPal will automatically cancel a a new members payment and profile as soon as they register. It happens sporadically and I have ensured that the user is not accidentally cancelling the profile/payment themselves.

Here is a screen shot of what the PayPal screen shows: http://dl.dropbox.com/u/5922669/paypal%20cancel.png

Here is a screenshot of the users receipt: http://dl.dropbox.com/u/5922669/Paypal%20receipt.png

Here are the PayPal logs:

http://dl.dropbox.com/u/5922669/paypal-rtn.log
http://dl.dropbox.com/u/5922669/paypal-ipn.log
http://dl.dropbox.com/u/5922669/paypal-api.log

Sorry for my technical ineptitude, but is there something I am doing wrong or is there an error with the way payPal is handling my transactions? Thanks in advance.

Jeff

Jeff, and other transactions are going through just fine? What do you find in common between the transactions that give you this problem that could help find the reason behind them?

Could you update your s2Member to the latest release and see if the problem still exists?

I'm emailing Jason.

Thanks, Christian.

I am updated to the latest version of s2Member, at least according to my dashboard.

There doesn't seem to be a connection between the events that this is occurring on. They are different member levels and have been across a 10 day span. It's happened about three times. I'll keep looking for any common threads. It could very well be that 3 users did something wrong, but they all reported that they believed they did everything correctly. I'll have them try again (I haven't yet since I didn't want them to think I was trying to scam them to input their credit card 2 or 3 times before I knew if there was an issue).

I'll report back if the issue persists. Thanks!

Jeff

Thanks for the heads up on this thread.

I believe this behavior is attributed to a recently discovered bug in s2Member v111105.

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

Thanks, Jason. I really appreciate you looking into the issue. I'll update the patches and let you know if there is an issue.

Thanks again!