Sagepay Server Change, Protx and Magento
Occasionally, the folks at Varien are just a step behind the folks at places like Sagepay. When this happens, clients tend to get a little stressed – especially when they receive emails saying that servers are being changed and so their payment method needs to be updated. But don’t worry – the folks at the ecommerce web design are here to help!
This latest misstep is between Sagepay and Magento. The Sagepay payment servers are going to be moving at the end of September, so they’ve been very nicely letting their customers know that their modules need updating – and with plenty of notice, which I (for one) certainly appreciated!
At the time of writing, I couldn’t find an update for the Protx module for Sagepay built in to Magento 1.4.1. So, we updated it ourselves and decided to post it here on our Magento blog to help anybody else in a panic.
Find the file located at: App / Code / Core / Mage / Protx / Model / Standard.php
Then create a local copy (App / Code / Local / Mage / Protx / Model / Standard.php) and open it up in your favourite text editor (mine’s Dreamweaver CS5).
At about line 78 there’s a function called “getProtxUrl”. Presuming your site set to either Live or Test, change the respective URLs to
https://live.sagepay.com/gateway/service/vspform-register.vsp
and
https://test.sagepay.com/gateway/service/vspform-register.vsp
A quick note – this is for clients using the Sagepay Form method and Magento. If you’re signed up for the Sagepay Server method and are using the Protx Magento module, the links will be
https://live.sagepay.com/gateway/service/vspserver-register.vsp
and
https://test.sagepay.com/gateway/service/vspserver-register.vsp
Also – check out Rob and I in the new video from Creare!
