Jump to content


Member Since 03 Jul 2008
OFFLINE Last Active Apr 27 2017 08:42

Posts I've Made

In Topic: PayPal Standard Return

26 April 2017 - 12:31



Hi, You were headed in the right direction, the reason for my confusion woke me at 4a.m. -


I installed a fresh 2.3.4BS & and updated the PayPal App. Confusion arose because although the site admin showed the app version v5.018, running a file compare of the site pre & post update showed no differences.


Unfortunately, (you may be ahead of me already) the site compare was run on my PC scripts but I hadn’t downloaded after the update! At some point after the update I'd uploaded paypal_standard.php again (can't remember why).


Thank you for your time & help with this.


In Topic: PayPal Standard Return

25 April 2017 - 15:56

typos in my last post - s/b:  "paypal_standard.php is wrongly showing checkout_process instead of checkout_success".

In Topic: PayPal Standard Return

25 April 2017 - 15:52



Hi, The auto-return address in my PayPal account and the return address in the process_button() parameter are both checkout_process.php.


Unless I have made a major mistake somewhere, I can only assume that the return in the after_process() function in 2.3.4BS Edge paypal_standard.php is wrongly showing paypal_process, it should be paypal_success, also, paypal_standard.php is not updated by the PayPal App Auto Update??


In Topic: PayPal Standard Return

25 April 2017 - 10:52



Hi, Thank you for your reply. I felt that the last line of function after_process in paypal_standard.php should redirect to checkout_success.


I am confused because:

  •     A fresh download of 2.3.4BS Edge has the redirect to checkout_process.php
  •     After installing 2.3.4BS Edge and hitting the PayPal App Update button in admin, no changes were made to paypal_standard.php. The admin>paypal>configure page shows “PayPal App v5.018”
  •     The PayPal App add-on, 9184, is v5.010. In this, paypal_standard.php redirects to checkout_success.php but it has some code which is not in the 2.3.4 script and it doesn’t have the hard-coded file/table names.
  •     Last November I asked -
        “The last line in function after_process()
             is                 tep_redirect(tep_href_link('checkout_process.php', '', 'SSL'));
            should it be  tep_redirect(tep_href_link('checkout_success.php', '', 'SSL'));  ?”

    and got the reply -

            “tep_redirect(tep_href_link('checkout_process.php', '', 'SSL'));

            is correct”


 I don’t know if I’ve gone wrong somewhere because I’m surprised that no-one else appears to have had the problem?


In Topic: OSC 2.3.4 PayPal Standard 3.2 could not verify transaction ....

21 April 2017 - 10:06

There are probably various reasons for this one of them being (I think) if you don’t have the correct TLS/OpenSSL level. Try creating & running the following script (the echo’s can probably be removed leaving just 3 lines):

<?phpecho '<br>A: ';
$ch = curl_init(); curl_setopt($ch,CURLOPT_URL, "https://tlstest.paypal.com/");curl_setopt($ch, CURLOPT_SSLVERSION, 6); var_dump(curl_exec($ch));
echo '<br><br>B: ';
echo '<br><br>C: ';
echo '<br><br>D: ';
echo '<br><br>---- ';

If correct it should output something like:


A: PayPal_Connection_OKbool(true)

B: string(0) ""

C: array(9) { ["version_number"]=> int(467968) ["age"]=> int(3) ["features"]=> int(34493) ["ssl_version_number"]=> int(0) ["version"]=> string(6) "7.36.0" ["host"]=> string(23) "x86_64-redhat-linux-gnu" ["ssl_version"]=> string(14) "OpenSSL/1.0.1e" ["libz_version"]=> string(5) "1.2.3" ["protocols"]=> array(20) { [0]=> string(4) "dict" [1]=> string(4) "file" [2]=> string(3) "ftp" [3]=> string(4) "ftps" [4]=> string(6) "gopher" [5]=> string(4) "http" [6]=> string(5) "https" [7]=> string(4) "imap" [8]=> string(5) "imaps" [9]=> string(4) "ldap" [10]=> string(5) "ldaps" [11]=> string(4) "pop3" [12]=> string(5) "pop3s" [13]=> string(4) "rtsp" [14]=> string(3) "scp" [15]=> string(4) "sftp" [16]=> string(4) "smtp" [17]=> string(5) "smtps" [18]=> string(6) "telnet" [19]=> string(4) "tftp" } }



If it shows an error you probably need to speak to your host provider.