A client of ours needed to upgrade to a direct payment method for SagePay, so with Ebizmart’s Sagepay approved extension, we grabbed a copy and popped it on. Unfortunately, it wasn’t long before we started experiencing problems. We have contacted Pablo @ Ebizmarts who was relatively receptive about the issues, hopefully, they will be fixed in the next release.
If we experience any other faults with the extension, we’ll be sure to update this post (although, for a “paid” extension, I’m hoping that isn’t the case).
Incorrect processing status
Even though there is an option to change the processing (after payment is authorised) status in System > Configuration > Payment Methods, it appears that this field is ignored. This is a quick fix thankfully.
Editing ./app/code/local/Ebizmarts/SagePayServer/controllers/PaymentController.php on line +503, change
$status = Mage_Sales_Model_Order::STATE_PROCESSING;
To
$status = Mage::getStoreConfig(‘payment/sagepayserver_moto/order_status’);
Then you also need to uncomment these lines,
/*$order->setState(
$status, false,
Mage::helper('sagepayserver')->__('Invoice #%s created', $invoice->getIncrementId())
);*/MOTO order creation in backend fails
It is not possible to create an order in the backend (one of the main features of this extension), because of an incorrect class name. Fortunately, changing this is an easy fix.
Editing ./app/code/local/Ebizmarts/SagePayServer/controllers/PaymentController.php on line +140, change
if(class_exists('Ebizmarts_SagePayServerDot_Helper_Data')){
To
if(class_exists('Ebizmarts_SagePayServer_Helper_Data')){
David
3 Sep. 2010
Thanks for these tips, very useful. It’s a great module and the Ebizmarts team have been receptive to bug reports.