Community Support Forums

Hi, I'm using s2Member Pro on Wordpress 3.2. Authorize.net is my payment gateway.

I was able to successfully complete a user registration and one-time payment, (in other words, I see my new user in wordpress and I received confirmation from my authorize.net acct that a payment was received) however the ONLY email I received was the generic Wordpress email with my username/password and a login URL. I didn't receive the Auth.Net signup confirmation email (with receipt) or the Specific Post/Page confirmation email.

I've seen in other posts that the Paypal.ipn log file is helpful in debugging. I wasn't able to glean help from looking at it, but maybe someone else can? Thanks in advance!

------------------
WordPress® v3.2 :: s2Member® v110620 :: s2Member® Pro v110606
parentingbydesign.com:443/?s2member_paypal_notify=1&s2member_paypal_proxy=authnet&s2member_paypal_proxy_use=pro-emails&s2member_paypal_proxy_verification=c8ea87abce7842f6936612e44355a5c2&s2member_paypal_proxy_return_url=
User-Agent: WordPress/3.2; http://parentingbydesign.com
array (
's2member_log' =>
array (
0 => 'Unable to verify POST vars. Possibly caused by a fraudulent request. If this error continues, please run IPN tests against your server from a PayPal® Sandbox account. They provide special diagnostic tools to assist you.',
1 => 'If you\'re absolutely SURE that your PayPal® configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect to PayPal® over an HTTPS connection.',
2 => 's2Member uses the WP_Http class for remote connections; which will try to use cURL first, and then fall back on the FOPEN method when cURL is not available. On a Windows® server, you may have to disable your cURL extension. Instead, set allow_url_fopen = yes in your php.ini file. The cURL extension (usually) does NOT support SSL connections on a Windows® server.',
3 => 'array (
\'s2member_paypal_notify\' => \'1\',
\'s2member_paypal_proxy\' => \'authnet\',
\'s2member_paypal_proxy_use\' => \'pro-emails\',
\'s2member_paypal_proxy_verification\' => \'c8ea87abce7842f6936612e44355a5c2\',
\'s2member_paypal_proxy_return_url\' => \'\',
\'txn_type\' => \'web_accept\',
\'txn_id\' => \'123456789\',
\'custom\' => \'www.parentingbydesign.com\',
\'mc_gross\' => \'1.00\',
\'mc_currency\' => \'USD\',
\'tax\' => \'0.00\',
\'payer_email\' => \'fakeemail@xxx.com\',
\'first_name\' => \'Name\',
\'last_name\' => \'Last\',
\'option_name1\' => \'Originating Domain\',
\'option_selection1\' => \'www.parentingbydesign.com:443\',
\'option_name2\' => \'Customer IP Address\',
\'option_selection2\' => \'11.111.11.11\',
\'item_name\' => \'$1 USD / One Time ( for 3 month access, non-recurring )\',
\'item_number\' => \'1::3 M\',
)',
),
's2member_paypal_proxy' => 'authnet',
's2member_paypal_proxy_use' => 'pro-emails',
's2member_paypal_proxy_verification' => 'c8ea87abce7842f6936612e44355a5c2',
)

I see. Thanks for posting the log entry right away, that helps a lot.

This part is what I'd focus on first:

0 => 'Unable to verify POST vars. Possibly caused by a fraudulent request. If this error continues, please run IPN tests against your server from a PayPal® Sandbox account. They provide special diagnostic tools to assist you.',
1 => 'If you\'re absolutely SURE that your PayPal® configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect to PayPal® over an HTTPS connection.',
2 => 's2Member uses the WP_Http class for remote connections; which will try to use cURL first, and then fall back on the FOPEN method when cURL is not available. On a Windows® server, you may have to disable your cURL extension. Instead, set allow_url_fopen = yes in your php.ini file. The cURL extension (usually) does NOT support SSL connections on a Windows® server.',

Please go over your Authorize.Net configuration and make double sure that everything is correctly entered and filled.

Also, I notice your custom value having the www while the website's domain mentioned earlier doesn't have it. This can cause trouble, please read this viewtopic.php?f=36&t=1066

Let me know if that helps.

Good call on the "www" - my SSL certificate includes the www while my wordpress install does not. I'll fix the inconsistency there and see if that solves the issue.

Thanks!

Cool. I hope that solves it.

That was the issue -thanks!

Great!