PayPal Sandbox Error. Please contact Support for assistance.

[cheezcake]

Hey Guys,

Using s2m pro here.

I searched the forums for this problem, but I did not find any answers related to my situation.

I walked through all of the steps for setting up the PayPal Sandbox Details, viz.

- entered the following info in s2m pro:
- special sandbox email
- api username
- api password
- api signature
- enabled the sandbox in s2m
- set up IPN/PDT
- created a new s2member pro form

and I still get the generic error:

Error. Please contact Support for assistance.

In the s2m pro logs, this is all that shows up (edited for privacy):

Code: Select all

[edited].com/membership-options/?s2member_level_req=1
-------- Input vars: ( Thu Aug 19, 2010 9:55:05 pm UTC ) --------
array (
  'METHOD' => 'DoDirectPayment',
  'PAYMENTACTION' => 'Sale',
  'EMAIL' => '[edited]',
  'FIRSTNAME' => 'Lord',
  'LASTNAME' => 'Cake',
  'IPADDRESS' => '192.168.0.1',
  'DESC' => '$30 dollars one time membership fee ( for 1 year access, non-recurring, no trial )',
  'CUSTOM' => '[edited]',
  'CURRENCYCODE' => 'USD',
  'ITEMAMT' => '30.00',
  'TAXAMT' => '0.00',
  'AMT' => '30.00',
  'L_NAME0' => '$30 dollars one time membership fee ( for 1 year access, non-recurring, no trial )',
  'L_NUMBER0' => '1::1 Y',
  'L_AMT0' => '30.00',
  'CREDITCARDTYPE' => 'Visa',
  'ACCT' => '************6985',
  'EXPDATE' => '082015',
  'CVV2' => '123',
  'STREET' => '123 Main Street',
  'CITY' => 'Miami',
  'STATE' => 'FL',
  'COUNTRYCODE' => 'US',
  'ZIP' => '33135',
  'VERSION' => '63.0',
  'USER' => '[edited]_1282081303_biz_api1.gmail.com',
  'PWD' => '1282081313',
  'SIGNATURE' => 'Aby1eODvq4wtC9l19wP3iucThHiSAx1dRIkmmf52G9uW5azv09cjVvAr',
)
-------- Output string/vars: ( Thu Aug 19, 2010 9:55:05 pm UTC ) --------

array (
  '__error' => 'Error. Please contact Support for assistance.',
)



Halp!

[cheezcake]

Bueller?

I really need help on this!

[Jason Caldwell]

Hi there. Thanks for your patience.
~ I sincerely apologize for the delayed response on our part.

This error would indicate that your server is not connecting to PayPal® at all. That generic error means that no data was received in the communication to PayPal®. Are you running a Windows® server perhaps?
If so, you may want to have a look at this thread:
viewtopic.php?f=4&t=414&p=2231&hilit=curl#p2338

Otherwise, I recommend these server tests before you continue.
Please upload these three files anywhere on your site.
~ All three files are inside of this zip distribution.

curl-fopen-tests.zip

(1.43 KiB) Downloaded 91 times

curl-test-http-google.php ( open in a browser, you should see Google's home page ).
curl-test-https-paypal.php ( open in a browser, you should see PayPal.com )
fopen-test-https-paypal.php ( open in a browser, you should see PayPal.com )

[cheezcake]

Hey Jason, what's up?

Windows server here. The only test that runs successfully is: curl-test-https-paypal

The other two (curl-test-http-google, fopen-test-https-paypal) fail on a blank page.

I should also mention that i have the "allow_url_fopen" option set "on" within my php.ini.

Can I force s2member to use one method and not another? Please let me know where you intuition says the code would need to be modified.

Thanks!

[Jason Caldwell]

Thanks for the reply. Much appreciated.

That's very interesting. It's usually the cURL test that fails on a Windows® server.

OK. So here is my recommendation.
Inside the functions.php file for your theme, add this line anywhere:

Code: Select all

add_filter ("use_curl_transport", "__return_true", 25);

[cheezcake]

Hey Jason,

I've done as you instructed. And I still receive the `Error. Please contact support.`

The line:

Code: Select all

add_filter ("use_curl_transport", "__return_true", 25);

Was added to the current theme's functions.php and still there is no progress.

I'm kind of at a loss, because WordPress Programming is not my forté, I cannot assist you further.
Perhaps you can point me to the relevant point in the code and I can hack around?

Let me know,

-- Briam R.

[Jason Caldwell]

Hi Briam. Thanks for reporting back.
~ Sorry to hear that.

Certainly...
Take a look at:
/s2member/includes/functions/utilities.inc.php

Line #22, defines this function to handle remote requests:

Code: Select all

function ws_plugin__s2member_remote ($url ...

Ultimately though, s2Member uses the WP_Http class that is built into WordPress.
http://wpseek.com/wp_http/

So I would also look at your WordPress® distribution file:
/wp-includes/class-http.php

In other words, s2Member's utility function does this:

Code: Select all

$body = wp_remote_retrieve_body (wp_remote_request ($url, $args));

[Jason Caldwell]

Another way to test your installation of WordPress:
Uninstall s2Member temporarily, to rule it out as a problem.
Then, pop this code into a file of your own and run some tests:

Code: Select all

echo wp_remote_retrieve_body (wp_remote_request ($url));

[cheezcake]

Sir I've tried all of these suggestions but nothing is working.

I am looking helpless in front of my management, and they are asking if there are alternatives to s2member pro.

We have invested time in trying to figure this out, but ultimately only you can help us as this is a product of your design.

Although I can program php, I am at a loss within your plugin due to the short time constraints.

Please help, I am searching for alternatives but I know you can help!

[Jason Caldwell]

Hi there. Thanks for reporting back on this topic, and thanks for your patience.

Based on ( your previous reports, the log file you sent over, and the tests that you ran ), this definitely looks like a connection issue to me; and although I can't say for sure, it sounds like you would have this issue with or without s2Member installed, due to the test results that came back.

My best guesses at this point:

- cURL is still enabled in your php.ini file?
( on Windows, I recommend running with cURL off,
because Windows typically has problems running cURL over HTTPS )

- You have a firewall installed that is preventing outbound/inbound connections over HTTPS, or specifically to PayPal servers. See: https://cms.paypal.com/us/cgi-bin/?cmd= ... echecklist

- You have another plugin installed that has modified the WP_Http class that comes with WordPress® in some way that is preventing connections over HTTPS, or specifically to PayPal servers.

- You have a server extension installed that is affecting the receiving end of HTTPS connections through the fopen method, or is otherwise requiring special parameters that are not built into the WP_Http class for WordPress®. http://planetozh.com/blog/2009/08/how-t ... wordpress/

If nothing gives, only headaches, please feel free to submit an FTP login to your web space.
I'll be happy to have a look for you. - please use this private contact form.

* If you can't provide an FTP login to your development installation, please send an FTP login to a temporary test installation so that further diagnostics can be run against your server configuration.

[cheezcake]

Hey Jason, I'm running some tests now, but I've sent you my FTP information.

Let me know what you find! =)

-- Briam R.

[Jason Caldwell]

Hi Briam. Thank you.

I just took a quick look at your server configuration.
It appears that your server is not configured for SSL connections at all. ( i.e. you're missing the openSSL extension ). I run some tests against the FOPEN method on your server with full error reporting, and I received this notice:

Code: Select all

Notice: file_get_contents() [function.file-get-contents]: Unable to find the wrapper "https" - did you forget to enable it when you configured PHP?

You can have a look here for additional details on this error if you like:
http://www.google.com/search?q=Unable+t ... 22https%22

My recommendations:
1. Disable cURL in your php.ini file. It does not jive with HTTPS on a Windows server.
2. Enable the php_openssl.dll extension so that support for HTTPS will be enabled for the fopen method.
3. Re-run the php test file that I placed on your server:
fopen-test-https-paypal.php ( you should be good then )

[Jason Caldwell]

Example php.ini file changes:

Code: Select all

;extension=php_curl.dll
extension=php_openssl.dll
allow_url_fopen = on


You'll need to restart Apache after these changes. If that still does not work, you may need to actually install openSSL, as it may not be installed on your server at all. Short of this, I recommend a pre-configured server from a reputable hosting company, such as MediaTemple (gs), MediaTemple (dv), BlueHost, HostGator, Rackspace, or the like.

[cheezcake]

Thank you Jason!!! That worked perfectly... I knew you could help!

Just as an aside, where did you see the debug information? I even tried looking in the Apache error logs and could not find any debug output whatsoever.

Thanks! You're great!

-- Briam R.

[Jason Caldwell]

Great to hear that Briam.
~ You're VERY welcome.

I just ran this test file, and I forced error_reporting to E_ALL for debugging:

Code: Select all

<?php
ini_set("display_errors", true);
ini_set("error_reporting", E_ALL);
echo file_get_contents("https://www.paypal.com/");
?>

[cheezcake]

Hey Jason,

I just figured out that one of our projects relies very heavily on cURL. It seems disabling cURL outright is not the best option. Is there anyway to explicity tell s2member to leave cURL be?
When I disabled cURL and enabled SSL support for the fopen method, everything runs fine. Curl somehow seems to upset things. Can I explicitly declare unto WordPress that it cannot use cURL?

Thanks!

[cheezcake]

Jason!

I have a solution! I will post it as soon as I get a chance to sit down.

Thanks!

[Jason Caldwell]

Can I explicitly declare unto WordPress that it cannot use cURL?

Yes, just add this to the functions.php file for your WordPress® theme:

Code: Select all

add_filter ("use_curl_transport", "__return_false", 25);

[apage8]

Hi Jason,

I'm running into some similar issues and have searched the forums in search of an ansewr... Paypal is not redirecting to the registration page or sending an email with the registration list/confirmation. I've gone through all the settings multiple times and everything looks correct. However, I ran the 3 tests that you posted above and the curl-test-http-google.php test did not work correctly. I got a blank page. Any suggestions on what I should do next? The site is running on a Linux server.

I look forward to your response, this is extremely time sensitive and holding up the launch of a site. Thanks in advance!