Possible bug - IPN item handling since 221028?

#9

Could you show me the button/pro-form shortcode you’re using? So I use the same details to reproduce it in my setup.

Thanks! :slight_smile:

#10 
[s2Member-Pro-PayPal-Form level="2" ccaps="books,magazines,gifts" desc="$15 USD / One Time (for 1 month access, non-recurring, no trial)" ps="paypal" lc="" cc="USD" dg="0" ns="1" custom="booksmagazinesgifts.com" ta="0" tp="0" tt="D" ra="15" rp="1" rt="M" rr="BN" rrt="" rra="2" accept="paypal,visa,mastercard,amex,discover,maestro,solo" accept_via_paypal="paypal" coupon="" accept_coupons="0" default_country_code="" captcha="0" /]
1 Like
#11

Thank you!

#12

Downgrading to 220925 both Framework and Pro solved the problem for me as a workaround. You should consider recalling the 221028 and 221030 update to spare your users the pain…

1 Like
#13

Thanks for the update.

I’m trying to reproduce what you reported with 221030, using the details from your shortcode, and didn’t have that problem. The user was created, got access for one month, and the EOT time was set correctly for Nov 30th.

Could you send me the log files with the entries where you saw that happen so I can review them? Thanks!

#14

with 221030 now: The membership duration of 1 month is only 1 day
users get their EOT -1 email just after making payments

The EOT -1 email would be because the user got 1 Day, so today was the day before already. But I’m still not sure how the 1 Day thing happened, couldn’t reproduce it yet. My tests are fine so far with v221030… Was that a new signup, or a resent IPN of a signup done with v221028?

PayPal ERROR: Unexpected txn_type/status
#15

I realized I did not have the logfiles on but I signed up various new test accounts with 221030 and paid for a 1 month membership via PayPal (real payment, no sandbox!) and the users had an EOT of Oct 31st 2022.

When I downgraded and went through the same exercise again (new user signup, payment through PayPal), the EOT was correct.

So it should not be the shortcode but something else…

#16

And the EOT -1 Email was only sent out in version 221028, not in the ones I tried in 221030…

#17

Thanks for the additional details.

Thanks for clarifying that.

Ah ok, got it.

Thanks for confirming the version for that behavior. It’s strange, I still can’t reproduce it. Been doing several tests since we started talking about this, and the EOT is set correctly for me. Would have loved to see your log files for those. If you feel like reproducing the behavior with logging enabled, please send me the logs.

And again, I’m really sorry about the inconvenience that caused you.

#18

Hi

We’re running Version 221031 + s2Member Pro v220421 and can report a similar problem.
The renewing members appear to be demoted 5 to 10mins or so after paying (rather than 365 days) - examples below.

The last successful EOT set appears to be Fri Oct 27th, 2022

Successful payment at: 1 Nov 2022 12:29:04 GMT
Demoted by s2Member: Tue Nov 1, 2022 12:38 pm UTC
Paid Subscr. ID @ time of demotion: paypal → 20Y248*********

Transaction date
31 Oct 2022 21:54:22 GMT
Demoted by s2Member: Mon Oct 31, 2022 9:59 pm UTC
Paid Subscr. ID @ time of demotion: paypal → 6AS2***********

#19

Hi P,

I see. I would like to have a look at your logs. If you haven’t yet, could you enable logging, and reproduce the behavior, so we get some entries to look at, please? WP Admin > s2Member > Log Files

Because I haven’t been able to reproduce that behavior in my tests, and I need to see what’s going on in your setup, please.

If you can show me also the shortcode you’re using. if you’re using the Paypal pro-form, could you tell me the kind of PayPal account you have?

Are these new signups, or existing user upgrades?

I look forward to the new details, to attempt reproducing it on my side.

:slight_smile:

#20

Thanks for getting back so promptly Christian

I’ll need to clone the site and run some test transactions with the logs enabled - please bear with me.

Here is an example: [s2Member-PayPal-Button level=“2” ccaps="" desc="(Category L) Student Membership" ps=“paypal” lc="" cc=“GBP” dg=“0” ns=“1” custom=“ourdomain.uk.com” ta=“0” tp=“0” tt=“D” ra=“35.00” rp=“1” rt=“Y” rr=“BN” rrt="" rra=“1” image=“default” output=“button” /]

We’re using the Button Code Generator - not the Paypal pro-form.

And these are membership renewals.

Thanks for your help.

#21

What’s the best way to send the log files to you Christian?

#22

Thanks for the additional details.

If you’re cloning it so you can enable logging, that’s not needed. It’s fine to have logging while troubleshooting, even if it’s a live site. What’s better not to do is leave it enabled all the time when it’s not needed. Now, if you want to clone it to do tests, that’s fine.

Are these renewals started by the member clicking on the button, or are they payments that come in from an active subscription?

You can click on my name, and then the blue “message” button to message me privately the logs or access.

:slight_smile:

#23

Thanks Christian - messaged directly.

1 Like
#24

I right now cannot help debugging because in Nepal hiking, but I have exactly the same problem, 1dsy instead of 1 year added for stripe, maybe also PayPal pay once payments

#25

New users are fine, does happen on re activation of a user (have to check about simply adding time to not yet demoted user)

#26

Happens on both PayPal and Stripe. I didn’t yet have a prolonge payment on an active account.

Please immediately publish a new version based on the old one. Theese two updates should never have been paid published. This error is about as bad as it can get

#27

I agree. https://s2member.com/s2member-v221103-now-available/

I removed the changes to these files (notification and return ones) in the last couple of releases. These are back to how they were in v220925. Any of the new issues mentioned above should be gone with this one.

#28

Looks like its working correctly now Christian :sweat_smile:

Thanks for your prompt help.

1 Like