fleeced Posted April 24, 2019 Share Posted April 24, 2019 Had an email from a customer who couldn't pay with Nochex tonight. So I tried my checkout and I got a bust checkout page at Nochex as well. The Nochex module redirects to https://www.nochex.com/nochex.dll/checkout We use Nochex and Paypal and I have had a Nochex order from 3 days ago. Can't see any changes or complaints on Twitter etc I stuck that url above in Google and found a store that seems to use a different url and that seems to work. Thoughts? https://i.postimg.cc/2SLjQ1VV/elite-nochex.png https://secure.nochex.com/default.aspx Link to comment Share on other sites More sharing options...
♥14steve14 Posted April 25, 2019 Share Posted April 25, 2019 What do Nochex say. They would be the ones to ask. REMEMBER BACKUP, BACKUP AND BACKUP Link to comment Share on other sites More sharing options...
jameslugton Posted April 25, 2019 Share Posted April 25, 2019 Hello fleeced, The url that you have mentioned: https://www.nochex.com/nochex.dll/checkout is an old checkout url. The url that is now commonly used is: https://secure.nochex.com/default.aspx. As a solution to your issue, We have an up-to-date Nochex module for oscommerce on the Nochex GitHub here: https://github.com/NochexDevTeam/osCommerce which uses the url https://secure.nochex.com/default.aspx along with updated functionality / features. Alternatively If you prefer how your current module works, can you raise a support ticket: https://support.nochex.com with a copy of your Nochex page so I can make the necessary changes for you Kind Regards James Lugton - Nochex Technical Support Link to comment Share on other sites More sharing options...
fleeced Posted April 25, 2019 Author Share Posted April 25, 2019 Thanks @jameslugton How long since the url was changed?? We have had orders through this month and previous months going to this old url which seem to have checked out fine so not sure how that could happen if that page has been as broken as it is now. Would have been nice to have a decent error page, rather than just a broken one perhaps with a prompt with maybe a message to contact the merchant or something "This is an old payment page, please contact the store owner". Luckily, we were contacted by a customer but could have been weeks before we knew otherwise. At the moment, just a change to the new url has done it for us and it is working now but will look at the Github project too and perhaps do a full install of that module Line 30 in /home/**/public_html/includes/modules/payment/nochex.php ``` if (is_object($order)) $this->update_status(); //$this->form_action_url = 'https://www.nochex.com/nochex.dll/checkout'; $this->form_action_url = 'https://secure.nochex.com/default.aspx'; } ``` Link to comment Share on other sites More sharing options...
jameslugton Posted April 25, 2019 Share Posted April 25, 2019 Hello Fleeced, The old url may have stopped working recently but will take a look into this further along with the error page you / your customers have received. The secure.nochex.com url is the better url to use and has been around for sometime. The latest versions of our module for osCommerce have the secure link. I am glad you have managed to get your module working by changing the url, and if / when you come to updating your Nochex module and experience any issues or would like any assistance. Please get in touch, and I will be more than happy to assist you. Kind Regards James Lugton - Nochex Technical Support Link to comment Share on other sites More sharing options...
fleeced Posted April 25, 2019 Author Share Posted April 25, 2019 @jameslugton That old broken url does need addressing as it will cause thousands of stores to lose money from lost orders and lost commissions for Nochex as well. Can anyone with a Github account please raise an issue to change the URL in the file below https://github.com/gburton/Responsive-osCommerce/blob/master/includes/modules/payment/nochex.php Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.