We started to receive some interesting issues with our installation and the checkout procedure. When a customer would click “Submit Order” there would be a 15 second delay and then a jscript popup saying “There was an error processing your order …” We would then receive a “Payment Transaction Failed Reminder” email immediately after that would state the reason as “Unable to read response, or response is empty”. Any PayPal transaction would go through successfully even though the denial email and notice to the customer. This transaction would routinely go through anywhere from 1-4 times for each transaction (I assume the customer was continuing to click “Submit Order” for some bad reason). After the payment though, Magento had no clue the order happened. It would not show anything regarding the order. Attempting to delete an existing order, or changing the status of an existing order will also cause the same “Unable to read response, or response is empty” error.
The exception.log showed the following…exception:
exception ‘Zend_Http_Client_Exception’ with message ‘Unable to read response, or response is empty’ in /home/XXXXX/public_html/mo/lib/Zend/Http/Client.php:855Stack trace:#0 /home/XXXXX/public_html/mo/lib/Zend/XmlRpc/Client.php(276): Zend_Http_Client->request(‘POST’)#1 /home/XXXXX/public_html/mo/lib/Zend/XmlRpc/Client.php(339): Zend_XmlRpc_Client->doRequest(Object(Zend_XmlRpc_Request))#2 /home/XXXXX/public_html/mo/app/code/local/Afa/Observer.php(37): Zend_XmlRpc_Client->call(‘order_placed’, Array)#3 /home/XXXXX/public_html/mo/app/code/local/Afa/Observer.php(88): Afa_Observer->affiliate_call(‘order_placed’, Array)#4 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Model/App.php(1239): Afa_Observer->model_saved(Object(Varien_Event_Observer))#5 /home/XXXXX/public_html/mo/app/Mage.php(303): Mage_Core_Model_App->dispatchEvent(’sales_order_sav…’, Array)#6 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Model/Abstract.php(292): Mage::dispatchEvent(’sales_order_sav…’, Array)#7 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Model/Abstract.php(252): Mage_Core_Model_Abstract->_afterSave()#8 /home/XXXXX/public_html/mo/app/code/core/Mage/Checkout/Model/Type/Onepage.php(559): Mage_Core_Model_Abstract->save()#9 /home/XXXXX/public_html/mo/app/code/core/Mage/Checkout/controllers/OnepageController.php(396): Mage_Checkout_Model_Type_Onepage->saveOrder()#10 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Controller/Varien/Action.php(376): Mage_Checkout_OnepageController->saveOrderAction()#11 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(248): Mage_Core_Controller_Varien_Action->dispatch(’saveOrder’)#12 /home/XXXXX/public_html/mo/app/code/core/Mage/Core/Controller/Varien/Front.php(158): Mage_Core_Controller_Varien_Router_Standard->match(Object(Mage_Core_Controller_Request_Http))#13 /home/XXXXX/public_html/mo/app/Mage.php(459): Mage_Core_Controller_Varien_Front->dispatch()#14 /home/XXXXX/public_html/mo/index.php(65): Mage::run()
I fought over this for a while and then decided to look a bit closer and saw “Afa_Observer”. Removing the AfA (Affiliates for All) folder killed off the entire website and caused every page to give an “Unable to read response, or response is empty”. So…a little more thinking and I removed the AfA extension altogether by deleting it from app/etc/modules and bingo. That fixed it.
The only way I can think of the AfA extension to cause this sort of thing (even though I installed it a year ago and hadn’t touched anything on the site in a month) is that either A) someone attempted to checkout via an affiliate link and that corrupted the AfA table; or B) the AfA side of things went down on their end (does their workings mess with the local stuff though? Not sure…)
So…not a very nice issue but a surprisingly easy fix.
Admin, Checkout, Error, Exception
