ozEworks

Good news.

The TLS change to Payeezy is a server level issue. No code in the osCommerce module needs changing. However to be fully PCI compliant, you do need to remove the partial card details the module stores unnecessarily. However PayEezy is making another change to its API and it will require a new osCommerce module.

I want to clarify where we can download "PayPal Payments Pro Hosted Solution Payflow Edition" which you need for PayPal Advanced accounts. Can someone tell me?

Suren are you trying to use Sandbox mode?

XE URL seems to now be http://www.xe.com/currencyconverter/convert/?Amount=1&From=USD&To=EUR

Is XE working for anyone? Oanda seems to have a new converter https://www.oanda.com/currency/converter/ but they do reference their old one here https://www.oanda.com/currency/classic-converter https://www.oanda.com/convert/fxdaily redirects to https://www.oanda.com/currency/converter/ I read some more. https://oanda.secure.force.com/AnswersSupport?urlName=Exchange-Rates-API-FAQ-s&language=en_US Looks like this is now a Paid Service via API http://developer.oanda.com/exchange-rates-api/

I believe it is not just oanda as xe is also getting errors. Warning: file_get_contents(http://www.oanda.com/convert/fxdaily?value=1&redirected=1&exch=USD&format=CSV&dest=Get+Table&sel_list=USD): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /home/XXXXXXXX/public_html/XXXXXXX/includes/functions/localization.php on line 14 Warning: file_get_contents(http://www.xe.net/ucc/convert.cgi?Amount=1&From=USD&To=USD): failed to open stream: HTTP request failed! HTTP/1.0 400 Bad Request in /home/XXXXXXXX/public_html/XXXXXXX/includes/functions/localization.php on line 25

Do you still support osCommerce? I don't see any reference to it on your actual site.

Just a note for people use the older MS2.2 / Rc2a USPS V4 module there are service name changes to Domestic you will need to make changing Standard Post to Retail Ground. It will be in several places in the code. Also the name changes from being Registered Mark to a Trademark. 'USPS Retail Ground tradmrk' => 'USPS Retail Ground tradmrk', Uninstall and reinstall to test. Don't forget to keep your USPS ID to add back when you reinstall. See https://www.usps.com...lease-notes.rtf Other changes (Flat Rate boxes as a container) do not seem to impact the old module. Switch your current module to $usps_server = 'stg-production.shippingapis.com' to test impact

Sorry I will

Just a note for people use the older MS2.2 / Rc2a USPS V4 module there are service name changes to Domestic you will need to make changing Standard Post to Retail Ground. It will be in several places in the code. Uninstall and reinstall to test. Don't forget to keep your USPS ID to add back when you reinstall. See https://www.usps.com/business/web-tools-apis/2016-jan-webtools-release-notes.rtf Other changes (Flat Rate boxes as a container) do not seem to impact the old module. Switch your current module to $usps_server = 'stg-production.shippingapis.com' to test impact

OK we will test it out on Rc2a site and let you know.

As usual with the USPS upgrade it is not just a rate change. There are service names changes as well. Is anyone looking at updating the Add On?

It would be good to get an official response from the osCommerce team but this will largely depend on what version of osCommerce you are running. the PayPal module you are using and your hosting environment. Over at Zencart (an old osCommerce clone) they say it won't effect the code but they have advised FOR THE TECHNICALLY-INTERESTED: PayPal's update is occurring in 2 stages: A VeriSign G2-to-G5 Root Certificate Upgrade, and then a SHA-256 SSL certificate. And, strictly speaking, those changes have NO IMPACT on the PHP code used in Zen Cart. But they do affect underlying server technologies used on your webserver. 1. VeriSign Root Certificate Upgrade: We've already tested Zen Cart against the PayPal sandbox, which is already using the Verisign G5 Root Certificate, and it works fine. But that's because the webservers we tested on already have the Verisign G5 Root Certificate authority files installed. Your host can help you with this. See the link below. 2. SHA-256 SSL certificate PayPal isn't updating the "api-3t.paypal.com" endpoint (used in Zen Cart v1.3.x and v1.5.x) until June 2016 (and sandbox too, so we can't test that just yet; nevertheless, it's a server config thing, not a Zen Cart thing). But in 2015 there is a big push for all webservers to start using SHA-256 SSL certificate chains. As such, you should ensure that your hosting company properly updates your server's SSL certificate store. a) PayPal offers some advice for your hosting company here: https://ppmts.custhelp.com/ci/fattac...20English).pdf b) And you can also ask your hosting company to fix any SSL problems reported for your site as mentioned in #3 above.

We have successfully implemented UPS dimensional shipping. It does require some fine tuning in terms of product dimensions and box sizes to get it to calculate correctly but that effort is largely on the user side although we did have to add a debugger to see what was being sent to UPS so we could then match rates with their site.