Jump to content

Harald Ponce de Leon

  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by Harald Ponce de Leon

  1. it appears to be with Pay Pal standard only that they are removing commas for the thousands point. I attempted to check your demo.. but for the life me of I cannot remember the pass I used on that site and the pass forgotten email never came LOL


    It's a demo site - create another dummy account :lol: 


    I just looked through the git history of the payment modules - the PayPal modules were updated around Dec 4, 2007 (for the v2.2RC2 release on Jan 15, 2008) where the amount sent to PayPal changed from using the PHP number_format() function (using "," as a thousands separator) to a custom function where only a decimal separator is used.


    If you've experienced issues after that date, it could be possible that a third party add-on/module was used that still uses number_format() and the thousands separator to format the order total value.

  2. v5.018 has just been pushed out with the support for a custom stylesheet file to be loaded on the shopping cart page. This will only be loaded if the file exists (it does not as part of the PayPal App package) and will never be modified by the App's online update routine.


    Documentation for the available id's and the location and filename for the custom stylesheet file can be found at:



  3. @@Roaddoctor Can you check and confirm on the osCommerce Administration Tool -> Tools -> Server Info page that the curl extension is enabled in your PHP installation? Searching for "curl" on the page will bring you to the curl extension information and even show you the SSL Version it is compiled with.

  4. @@birdiebitsnbites TLS v1.2 support was first added in cURL v7.34.0 (in 2013) and in OpenSSL v1.0.1 (in 2012). The cURL package may need to be updated on your web server which may trigger a system wide upgrade depending on the operating system dependencies.

  5. @@Roaddoctor Try changing the SSL Version parameter in the PayPal App General settings page.




    This parameter and the Test Connection button was added in v5.010.


    If the connection fails for both Default and TLV v1.2 settings, try disabling the Verify SSL parameter. If connections work with Verify SSL disabled but fail when it is enabled, you'll need to update your server environment to be able to verify SSL certificates correctly.

  6. Strange, the files in catalog have been updated successfully, but there is a new /admin folder containing only paypal.php, copyrighted 2017 the file(s) in my actual admin folder seem not to have been updated.


    What paths are shown in the update logs in includes/apps/paypal/work/update_log-*.php? Your custom admin directory or hardcoded "admin"?

  7. it seems to me that the update process puts the paypal.php into the standard admin folder instead of the one being configured, is this an intended behaviour?


    There are no hardcoded paths when the files are being copied. For the admin files, it uses the DIR_FS_ADMIN parameter for the base admin path.


    The admin files in the zip package are located in the admin/ directory to keep them separate from the catalog files, however the online update routine detects this and copies the admin/ files to your DIR_FS_ADMIN path.

  8. Refreshed my test store and I'm receiving the following error from all the modules.


    Sandbox Server:


    Failed! Please review the Verify SSL Certificate settings and try again.


    The Verify SSL Certificate setting is not about your web server SSL certificate, it's about verifying PayPal's SSL Certificate when transactions are sent to their servers.


    Can you confirm that the following files exist:


    1) ext/modules/payment/paypal/paypal.com.crt, or

    2) includes/cacert.pem


    If those files exist and you are still getting the same error, disabling the Verify SSL parameter on the PayPal App -> Configuration -> General page will allow transactions again. This is only a temporary solution though, it is highly recommended to get your web server environment working with this parameter enabled.


    More information is available here:



  9. The update is still failing. I noticed that when I went to download the latest version from the Addons section, the latest version available is 5.010. Is the update sourced from a different location?


    It's not going to help, but v5.014 was just pushed out. You will need to get your server to download v5.011 first though.


    If your dev servers are publicly available, I would love to get access to it to see where the problem is. If that is possible, please email me the url, admin login, and FTP or shell login details and I'll have a look at what the problem is.

  10. @@Supertex It looks like the following high-severity fix for v2.3.3 (August 2012) is related:




    The normal behaviour is the reload of the checkout confirmation page redirects the customer to the start of the checkout procedure again at the checkout shipping page, due to the cart ID being changed.


    This is the bug report:



  11. @@kymation I can't repeat it and see others successfully downloading the update packages.


    Could you perhaps check if any PHP errors are being logged on your side? The following code can log PHP errors to a file:



    ini_set('log_errors', true);
    ini_set('error_log', DIR_FS_CATALOG . 'includes/work/errors-' . date('Ymd') . '.txt');


    (the work directory needs to be writable by the web server)

  12. I don't know why the module would not be installed. It's not possible to install the module in the traditional manner as it will redirect you to the Braintree App Configuration page.


    Try deleting the OSCOM_APP_PAYPAL_BRAINTREE_CC_SORT_ORDER parameter from your configuration table:



    delete from configuration where configuration_key = 'OSCOM_APP_PAYPAL_BRAINTREE_CC_SORT_ORDER';


    Then visit the Braintree App Configuration page and it should auto-install the module for you.

  13. The module is PCI compliant (both older module version and newer App versions). The card data never touches your server - Braintree process it directly via javascript and return a token which the module uses. The same goes for stored/vaulted cards - this is safe to enable for your customers.

  14. Thanks for pointing the error out. I can confirm the problem is using empty() on a constant (this produces an error on PHP < 5.5 Servers).


    An update will be pushed out within a few hours.