so is the hack only for pro?
No, this is for the s2Member Framework, the free version.
so is the hack only for pro?
No, this is for the s2Member Framework, the free version.
Iâm bringing this old topic back up again - I think this happened because paypal timed out, right?
I still see this problem on about 0.5% of all subscription transactions.
On some days it happens a lot - e.g. 01. May was crazy. Then many days happens never. Usually it happens for several transactions in a short timeframe (but not for every transaction during that timeframe, only about 1/3).
It rarely happens on new sign ups (maybe like 1 out of 1000) - but happens pretty often for subscriptions! Now in this case the user pays, the IPN log shows:
LOG ENTRY: Sun Jun 27th, 2021 @ precisely 11:51 am UTC
PHP v8.0.5 :: WordPress v5.7.2 :: s2Member v210526 :: s2Member Pro v210526
Memory 9.56 MB :: Real Memory 4.00 MB :: Peak Memory 9.72 MB :: Real Peak Memory 4.00 MB
openmtbmap.org/?s2member_paypal_notify=1
User-Agent: PayPal IPN ( https://www.paypal.com/ipn )
Array
(
[s2member_log] => Array
(
[0] => Unable to verify $_POST vars. This is most likely related to an invalid configuration of s2Member, or a problem with server compatibility.
[1] => Please see this KB article: http://www.s2member.com/kb/server-scanner/
. We suggest that you run the s2Member Server Scanner.
[2] => array (
âs2member_paypal_notifyâ => â1â,
then the confidential data
Now this is very troublesome as I need s2member to behave correctly on subscription payments too - else the customer does not get an invoice. The customers are alright - all the data is correct. So often the payment for the same customer went through correctly for a couple of years - only then on that day to get that unable to verify error.
Did this fix miss subscriptions payments? Or does this fix simply not loop long enough if it cannot contact the paypal servers?
If I send the IPN again from paypal (of course only possible within 7 days) then usually (as this bug is rare) it will work well.
Yes before this patch this happened even more often - as new payments were affected very often too.
It would really be good if this could be fixed for subscriptions too! Or change the loop to run 2-3 times as long if maybe on subscriptions it takes longer?
On another 0.5% of subscription payments - I receive a subscription payment from paypal - and it does not show in any log! Paypal shows IPN received however in the IPN dashboard⌠I think those would be even harder to analyse what is happening (again happening to subscribers were the subscription worked just fine in previous payments).
oh yeah - I am sure every user of s2member using paypal subscriptions is affected by this bug. However if you do not run any custom events like invoices firing on subscription payment arriving - you will not notice.
Every quarter I download all invoices that I sent out, download the logs from paypal and stripe - then check if for every payment an invoice was written in spreadsheet - and then manually create invoices for all missed payments.
Sometimes the whole payment is missing in the IPN log. Sometimes (more often) the above error. Not sure what to do about payments where the IPN log is not recording anything.
here is a full log with personal details starred out :
LOG ENTRY: Sun Jun 27th, 2021 @ precisely 11:51 am UTC
PHP v8.0.5 :: WordPress v5.7.2 :: s2Member v210526 :: s2Member Pro v210526
Memory 9.56 MB :: Real Memory 4.00 MB :: Peak Memory 9.72 MB :: Real Peak Memory 4.00 MB
openmtbmap.org/?s2member_paypal_notify=1
User-Agent: PayPal IPN ( https://www.paypal.com/ipn )
Array
(
[s2member_log] => Array
(
[0] => Unable to verify $_POST vars. This is most likely related to an invalid configuration of s2Member, or a problem with server compatibility.
[1] => Please see this KB article: http://www.s2member.com/kb/server-scanner/
. We suggest that you run the s2Member Server Scanner.
[2] => array (
âs2member_paypal_notifyâ => â1â,
âmc_grossâ => â13.00â,
âinvoiceâ => '5770e8562fbd7~193.171.196.â,
âprotection_eligibilityâ => âEligibleâ,
âaddress_statusâ => âconfirmedâ,
âpayer_idâ => 'XLQNRYGZ9K**â,
âaddress_streetâ => âKra****â,
âpayment_dateâ => â04:50:23 Jun 27, 2021 PDTâ,
âpayment_statusâ => âCompletedâ,
âcharsetâ => âwindows-1252â,
âaddress_zipâ => â8020â,
âfirst_nameâ => ââ,
âoption_selection1â => âopenmtbmap.orgâ,
âoption_selection2â => '193.171.196.â,
âmc_feeâ => â0.70â,
âaddress_country_codeâ => âATâ,
âaddress_nameâ => â****â,
ânotify_versionâ => â3.9â,
âsubscr_idâ => 'I-VP2Y4RM24â,
âcustomâ => 'openmtbmap.org|193.171.|AT|AT|+43-â,
âpayer_statusâ => âverifiedâ,
âbusinessâ => '@gmail.comâ,
âaddress_countryâ => ââ,
âaddress_cityâ => âGrazâ,
âverify_signâ => âAF7tNjcPnsOKC0KShsgTPKk***************â,
âpayer_emailâ => â<@gmail.comâ,
âoption_name1â => âOriginating Domainâ,
âoption_name2â => âCustomer IP Addressâ,
âtxn_idâ => '8D199â,
âpayment_typeâ => âinstantâ,
âlast_nameâ => 'â,
âaddress_stateâ => ââ,
âreceiver_emailâ => â*****@gmail.comâ,
âpayment_feeâ => ââ,
âreceiver_idâ => 'Z89X4K6â,
âtxn_typeâ => âsubscr_paymentâ,
âitem_nameâ => âFirst year access for âŹ20, then âŹ13 each year (recurring_charge, for OpenMTBMap access)â,
âmc_currencyâ => âEURâ,
âitem_numberâ => â1â,
âresidence_countryâ => âATâ,
âtransaction_subjectâ => âFirst year access for âŹ20, then âŹ13 each year (recurring_charge, for OpenMTBMap access)â,
âpayment_grossâ => ââ,
âipn_track_idâ => '*â,
)
)
)
BTW - I*m still from time to time running into the Unable to verify $_POST vars.
Usually resending the paypal IPN will always work. So I think sleep should be extended to 5 seconds over 3 seconds - and another full round of tries should be done.before aborting.
If s2member aborts then the user isnât created or the payment not credited to the account / or user not demoted when the payment failed. With 5 seconds over 3 seconds it helps already again a tiny bit.
Also sleep 3 means anything from 2-3 seconds. Sleep 5 anything from 4-5 seconds.
I had a customer email me the other day saying they received âError. Please contact Support for assistance.â when trying to renew. They eventually got it to work but only after trying 3 times.