Error on POST

[keifa]

Hello,

We've dbl checked our settings and are getting an error after a person subscribes via paypal:

Unable to verify POST vars. Please contact Support for assistance

This is most likely related to an invalid PayPal configuration. Please check s2Member -> PayPal options

Do you know what setting we might have wrong? The plugin has been updated.

Thanks,
Keith

[lunaKM]

I have the same problem I have run the IPN test through the sandbox and while the log places it in the array, I still get the POST vars error.

When I was testing with sandbox it worked flawlessly, but now that it's live and people are upgrading (current level 0 users) I get this issue.

[keifa]

I don't know where to turn. I emailed the company, but no response

[Jason Caldwell]

Thanks for your inquiry. I'm sorry to hear this is not working for you.

I have the same problem I have run the IPN test through the sandbox and while the log places it in the array, I still get the POST vars error.

When I was testing with sandbox it worked flawlessly, but now that it's live and people are upgrading (current level 0 users) I get this issue.

Here are some things I would check:

1. After you went live, did you update your PayPal Account Details inside s2Member?
( see: s2Member -> PayPal Options -> Account Details )
2. If so, did you also disable Sandbox mode?
3. Is your live PayPal Account, a "Business" account?
4. Are you using the Shortcode Button, or did you integrate the Full Button Code?
If you integrated the Full Button code, make sure you re-generate your Button Codes after you go live. The Full Button Code MUST be generated with Sandbox mode disabled. Otherwise, you will get this error; because a live transaction is being sent through the Sandbox.

[Jason Caldwell]

If my last response does not produce a solution for you, please contact me directly with a WP Dashboard login to your blog. I'll be happy to have a look for you. If it's a bug, I would certainly like to know about it.

[keifa]

Thanks Jason - I sent you a PM with more information. - Keitb

[Jason Caldwell]

I got your PM. ~Thanks.
So it sounds like the issue you're having, is specifically related to the Auto-Return/PDT configuration. I would double-check s2Member -> PayPal Options -> PDT Integration. Make sure that your PDT Identity Token ( provided by PayPal ) is the one for your "live" account, and NOT the one from Sandbox testing.

[keifa]

I sent you an em with login info Jason. Also, this is a windows server. Could that be an issue?

[Guest]

Just thought I'd chime in that I am experiencing the same issue.

Except, I'm currently testing in sandbox mode.

The email address I've used is the one for my sandbox business acct and the PDT key is the one from the sandbox business account.

Any ideas?

[keifa]

Jason - did you receive the login info via email? Keith

[keifa]

Hi Jason - I upgraded to the new version but it still doesn't work. Any ideas? You can login again to see... Thx Keith

[Jason Caldwell]

Investigating now.

[Jason Caldwell]

We've dbl checked our settings and are getting an error after a person subscribes via paypal:
Unable to verify POST vars. Please contact Support for assistance
This is most likely related to an invalid PayPal configuration. Please check s2Member -> PayPal options
Do you know what setting we might have wrong? The plugin has been updated.
Thanks, Keith

Hi Keith. Thanks for the Dashboard access.
Here is what my investigation uncovered.

1. I ran a test transaction and successfully reproduced the error that you're reporting.
( not good, so I continued )

2. I enabled logging under: s2Member -> PayPal Options -> Logging/Debugging
( nothing here but the same, POST VARS could not be verified, also not good )

3. I then uploaded /club/phpinfo.php
and I then discovered that you're running on a Windows server, with the cURL extension enabled. That's not a bad thing, but there are known issues with cURL on Windows, particularly with SSL connections, which are required by s2Member, in order to speak with PayPal.

4. I then uploaded these three test files:
club/curl-test-http-google.php ( connection failed here )
club/curl-test-https-paypal.php ( connection failed here )
club/fopen-test-https-paypal.php ( connection succeeded )

Conclusion. There seems to be an issue with the installation of cURL on your server. Fortunately, s2Member does NOT rely solely upon the cURL extension. s2Member can use a variety of methods, through the WP_Http class. The best method can be determined automatically by s2Member.

The problem on your server, is that cURL is installed ( which s2Member considers the best choice ). However, in your case, it's not ( because it's broken somehow ). So the solution that I recommend, is to disable the cURL extension, by editing the php.ini file on your server.

You'll find a line that looks something like this:

Code: Select all

extension=php_curl.dll

Change that to this ( disable it ):

Code: Select all

;extension=php_curl.dll

Then, restart your web server and run another test transaction.

@C/TODO :: In the next release of s2Member... determine if there is a way for s2Member to avoid this problem automatically whenever cURL is not working as expected in a Windows environment.

For the benefit of other readers.
Whenever possible, try to install s2Member on a Linux-based operating system. s2Member has been tested on Windows, and does work. However, the suggested hosting platform for WordPress, and also for s2Member is a Linux/Unix based operating system running Apache 2+ with PHP 5.2+
http://wordpress.org/hosting/


@COMPLETED/TODO :: In the next release of s2Member... determine if there is a way for s2Member to avoid this problem automatically whenever cURL is not working as expected in a Windows environment.

UPDATE:
This issue was addressed in the release of s2Member v3.2.

- Compatibility. On a Windows® server, the cURL extension is usually NOT compatible with SSL communications. s2Member now signals to the WP_Http class, that it should temporarily disable the cURL transport when a remote URL is being processed with an `https://` prefix. This allows the WP_Http class to recover gracefully (automatically) and fall back on the FOPEN method. If you're running WordPress® on a Windows® server, you should make sure that you have this inside your php.ini file. ( `allow_url_fopen = on` ). A symptom of this bug, was to see an error in your paypal-ipn.log file, with something like: `Unable to verify _POST vars...`.

[drbyte]

Hosting WP on a windows box is not recommended. Along with the issue above, it has a known issue with Custom Permalink structure.

[keifa]

Disabled curl and it's working now. Thanks!

[Jason Caldwell]

Disabled curl and it's working now. Thanks!

Great to hear that. Thanks for reporting back on this. Much appreciated.

[Jason Caldwell]

I have the same problem I have run the IPN test through the sandbox and while the log places it in the array, I still get the POST vars error.

When I was testing with sandbox it worked flawlessly, but now that it's live and people are upgrading (current level 0 users) I get this issue.

Investigating now.

[Jason Caldwell]

I have the same problem I have run the IPN test through the sandbox and while the log places it in the array, I still get the POST vars error.

When I was testing with sandbox it worked flawlessly, but now that it's live and people are upgrading (current level 0 users) I get this issue.

Investigating now.

Hi Luna. I WAS able to reproduce the error on your installation.
However, I was unable to find any problem with your configuration of s2Member. So I'll need FTP access to your /wp-content/ directory so that tests can be run. If you can provide FTP access, I'll upload some test files to your server and determine the issue for you.

[lunaKM]

I'll get FTP access set up and sent to you some time this morning when the BF is up.

[Jason Caldwell]

I'll get FTP access set up and sent to you some time this morning when the BF is up.

Still investigating. This appears to be a plugin conflict on your installation.

[Jason Caldwell]

Hi Luna. Investigation is completed.

Your installation of PHP is corrupted, or mis-configured somehow.

I created a test file with this inside it:

Code: Select all

<?php print_r($_GET); ?>

http://www.submissiveguide.com/get-test.php?test=1

This file should be outputting this, but it's NOT.

Code: Select all

array('test' => 1)

I would try contacting your hosting provider and asking them why
the $_POST / $_GET superglobals are empty.

FYI: I uploaded the same file to your /wp-admin/ directory, and it works fine.
http://www.submissiveguide.com/wp-admin ... php?test=1

Code: Select all

array('test' => 1)

[lunaKM]

Thanks Jason,

I'll look into it and get back with you with a follow-up.

[lunaKM]

We manage the server. Since we use Lighttpd instead of Apache we don't have htaccess files. Apparently we discovered that the rewrite regex was incorrect causing the superglobals to be blank.

We rewrote the regex for the rewrite rules in the config file. The test file you uploaded now works. I'll run a test upgrade once I finish moving this weekend and have internet back.

Thanks again.

[lunaKM]

Jason,

A user upgraded their account just now but the return from PayPal still failed. The user was not upgraded in the User Table. I have had to go in manually and upgrade them.

The Logs still indicate that it couldn't verify POST vars. The credentials I set up for you for testing are still in place. FYI I will be moving and without Internet this weekend.

[lunaKM]

Have you gotten a chance to look into this again?