Harald Ponce de Leon

@@Supertex It looks like the following high-severity fix for v2.3.3 (August 2012) is related: https://library.oscommerce.com/Online&en&oscom_2_3&release_notes&v2_3_3#upg23 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: http://forums.oscommerce.com/tracker/issue-473-improve-shopping-cart-id-detection/

@@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)

@@kymation That's a strange error as the website is online. Please try again in a short while and reply back if it works again for you or not. Thanks!

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.

Can you confirm that the following file exists: catalog/includes/modules/payment/braintree_cc.php

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.

If you can connect to sandbox now, you can continue to connect to live on June 30, 2017.

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.

The problem Henry experienced has been solved. If the PayPal Seller account has a API Certificate already set up, the API Signature cannot be used as the API Certificate already exists (PayPal only allows either a API Signature or API Certificate to be used). Removing the API Certificate from the PayPal account allows the Retrieve Credentials procedure in the osCommerce PayPal App to work and retrieve the API Credentials. It's not necessary to create the API Signature at PayPal, the Retrieve Credentials procedure will automatically do this for you.

Testing specific error cases can be performed by enabling Negative Testing on your sandbox seller account. This can be enabled at the PayPal Developer site, select Profile on your sandbox seller account, and Negative Testing can be found in the Settings tab. In your store installation, select a test product and change the price to one of the following error codes: https://developer.paypal.com/docs/classic/api/errors/express-checkout/ eg, error code 10485 has a product price of 104.85, error code 10486 has a product price of 104.86. This needs to be the total price so disable extra tax and shipping costs. All error codes I have tested return the customer back to the shopping cart page. If error 10486 is tested, the customer is redirected back to PayPal so they can select another funding source.

It is normal behaviour for both modules to be deactivated if the EC module is disabled. Here is a note shown when first enabling the DP module: Please note: Direct Payment is not a stand-alone product - you are required to enable and use Express Checkout together with Direct Payment. A similar note should be shown on the DP configuration page if EC is disabled however none is shown - I'm looking into this. A note is shown on the legacy Modules -> Payment Modules -> PayPal DP page, however it should also be shown on the App module configuration page. How are you getting PayPal to decline the EC payment? Cancelling the payment during EC should return the customer back to their shopping cart page.

@@wHiTeHaT could you create a screencast of the API Retrieval failing for your client and send me a link via email? The only error message I have on my side is an internal service error from PayPal - that could be the reason for receiving an rpcStatus of -110. If PayPal can see the problem occurring in a video, it can help see what the actual problem is. Thanks!

v5.011 has just been pushed out. It adds a compatibility layer for v2.3.4 BS Community Edition and is safe to upgrade to.

v5.011 has just been pushed out with a compatibility layer for v2.3.4 BS Community Edition. It is safe to update from v4.039 or later version. If you'd like to apply the update sooner, visit the PayPal App -> Info/Help page and the online update notification should appear.

A parameter to use the default cURL SSL version or force TLS 1.2 connections was added in v5.010. It's also possible to perform a test connection to make sure the parameter is set correctly. More information is available here: https://library.oscommerce.com/Package&en&paypal&oscom23&ssl_version

@f@bs add the following code to catalog/includes/functions/compatibility.php and catalog/admin/includes/functions/compatibility.php: // log errors if (is_dir(DIR_FS_CATALOG . 'includes/work') && is_writable(DIR_FS_CATALOG . 'includes/work')) { if (!is_dir(DIR_FS_CATALOG . 'includes/work/error_logs')) { mkdir(DIR_FS_CATALOG . 'includes/work/error_logs', 0777, true); } if (is_dir(DIR_FS_CATALOG . 'includes/work/error_logs') && is_writable(DIR_FS_CATALOG . 'includes/work/error_logs')) { ini_set('log_errors', true); ini_set('error_log', DIR_FS_CATALOG . 'includes/work/error_logs/errors-' . date('Ymd') . '.txt'); } } Errors will then be logged to the catalog/includes/work/error_logs/ directory. We need an error message here to help you out further.

Hi Fabrice.. The v2.3.5 release is based on v2.3.4 (not BS). The BS is a separate community release series. v2.3.5 is based on the previous v2.3 release series. The BS release series is incompatible to v2.3.x and will merge to v2.4 when the production ready release is pushed out.

It's up!

@@inra311 what is the order status when the customer lands on the checkout success page? This order status should have the "Downloads Status" flag enabled otherwise the download links will not show. This is set in the Admin -> Localization -> Orders Status page.

Hi Matt.. Sure do :) v4.039 to v5.000 https://github.com/haraldpdl/oscom2_app_paypal/compare/23-4.039...23-5.000 v5.000 to v5.001 https://github.com/haraldpdl/oscom2_app_paypal/compare/23-5.000...23-5.001 v5.001 to v5.010 https://github.com/haraldpdl/oscom2_app_paypal/compare/23-5.001...23-5.010 You can combine version numbers in the url, eg v5.000 to v5.010 https://github.com/haraldpdl/oscom2_app_paypal/compare/23-5.000...23-5.010

​Hi Mike.. The PayPal App for osCommerce Online Merchant has only been developed and certified for our v2.3 (and earlier) and v2.4(beta) release series. The PayPal App for v2.3 has been added to the BS/EDGE community release series, which is not compatible with the v2.3 release series. I'd suggest waiting until the App has been updated for BS/EDGE and performing the update manually. There is currently no update for our v2.4 release series as the update feature has moved to the core level and has not yet been pushed out in a v2.4 beta release (this is coming soon). If everything is working for you on BS/EDGE, I'd recommend waiting for the production ready release of v2.4 (coming at the end of March) and moving to that. There will be a push to move existing v2.3 and BS/EDGE users to v2.4 once the production ready release is pushed out. Users currently on v2.3 will experience no problems updating the PayPal App.

The updates are for our v2.3 release series and are not compatible with v2.4(beta) or BS/EDGE. Updates for the v2.4 release series will be taken care of as a core feature, not as a per-app feature, with the integration of the upcoming Apps Marketplace. A list of files that have changed between App updates will not be provided as Apps are self-contained and should not be locally modified (unless coded to support customizations). This is to keep the update procedure as simple as possible. There are a lot of file and directory permission checks being performed before the first file is even copied to your website installation - if these vigorous checks pass, then the update will occur without a problem. It is impossible to perform an update if a file permission problem has been detected - in these cases, a list of the files that need their permissions changed will be displayed.

@@Sam-AUST, visiting the PayPal App Info/Help page will force an online update check to be performed. Here, the View Update button will appear where a list of updates will be shown with their changelog.

v5.0.10 has just been pushed out! This includes using the suburb value as the street2 parameter for the payment modules. Thanks to Jack_mcs and greasemonkey for reviewing the address changes.

Yep. I'll look at how this can be optimized further. You should see the shipping address in the CallbackResponse log - if you create the same address in your store account and initiate a test order, you should get the same shipping rates that were passed to the customer. This would be safe to do on the live server as you'd only need to log into PayPal and not perform an actual order.