Bugs http://www.magentocommerce.com/boards/ Magento Forums en Copyright 2008 2008-09-05T16:29:11-08:00 Enabling EWay breaks checkout http://www.magentocommerce.com/boards/viewthread/12972/ http://www.magentocommerce.com/boards/viewthread/12972/#When:02:52:18Z Simply setting it to Yes (Direct) makes the checkout page not work on version 1.0.19870.4

Changing it to no fixes the checkout.

Any ideas?

Thanks a lot for the extension.

]]> 2008-07-24T02:52:18-08:00 A couple of possible issues http://www.magentocommerce.com/boards/viewthread/14545/ http://www.magentocommerce.com/boards/viewthread/14545/#When:21:18:37Z Phew, I have finished tearing my hair out.

1) Installing EWay automatically updates Magento without warning the user. Ouch!! It has taken me hours to update my customisations to work with 1.1.2. I had to start with a fresh installation.

2) Even on a completely fresh install of 1.1.2, installing Eway still goes and fetches and installs all the latest code as extensions. And, this breaks the checkout even if Eway itself is disabled or uninstalled. The Accordion stuff in the onepage checkout never activates the first stage, and viewing Firefox’s log reveals heaps of javascript errors with undefined things.

3) To get around this I fudged my way through installing Eway manually on top of a fresh install of 1.1.2 and got it working

4) But, it only installs things in the default theme, not in any custom themes that are present, so again I had to figure out which files and directories needed copying, and copy them over

1 and probably 2 are not Eway’s fault.

4, I don’t know if that is a “bug” or just standard operating procedure for Magento but if the latter, some documentation would be nice so as to know what to copy!

]]> 2008-08-09T21:18:37-08:00 eWay bug - data not prepared properly for XML http://www.magentocommerce.com/boards/viewthread/11467/ http://www.magentocommerce.com/boards/viewthread/11467/#When:22:15:48Z Hi,

Firstly, thanks for integrating the eWay gateway PHP into Magento!
Saved many people lots of time, including myself.

I installed it via Magento Connect quite easily, and everything was working with test and live accounts.
After a few days however, my client was getting reports of random transactions getting declined when payments were submitted to eWay.
The response message was a javascript alert right at the end of the payment process, and the transaction could not proceed:
“xml formatted to eway standards whitespace not allowed at this location”

I contacted eWay support, and they said this is becuase there was a ampersand or special character in the data somewhere.
Sure enough, the title of the product had an ampersand in it.  However, this didn’t seem right, as it is very common for products or addresses to have special characters in them. They should be prepared for xml / database etc.

The PHP example on the eWay site uses a straight version of htmlentities to prepare ALL XML inserts.
They recommended i use the full version formatted for UTF-8 e.g. htmlentities(trim($var),ENT_QUOTES,’UTF-8’)

I updated the page \Eway\Model\Direct.php to have html entity conversion on ALL variables, except the CC details which should be already parsed.

//        $this->getQuote()->reserveOrderId();
        $xml = "<ewaygateway>";
        $xml .= "<ewayCustomerID>" . $this->getCustomerId() . "</ewayCustomerID>";
        $xml .= "<ewayTotalAmount>" . ($this->getAmount()*100) . "</ewayTotalAmount>";
        $xml .= "<ewayCardHoldersName>" . htmlentities(trim($payment->getCcOwner()),ENT_QUOTES,'UTF-8') . "</ewayCardHoldersName>";
        $xml .= "<ewayCardNumber>" . $payment->getCcNumber() . "</ewayCardNumber>";
        $xml .= "<ewayCardExpiryMonth>" . $payment->getCcExpMonth() . "</ewayCardExpiryMonth>";
        $xml .= "<ewayCardExpiryYear>" . $payment->getCcExpYear() . "</ewayCardExpiryYear>";
        $xml .= "<ewayTrxnNumber>" . '' . "</ewayTrxnNumber>";
        $xml .= "<ewayCustomerInvoiceDescription>" . htmlentities(trim($invoiceDesc),ENT_QUOTES,'UTF-8') . "</ewayCustomerInvoiceDescription>";
        $xml .= "<ewayCustomerFirstName>" . htmlentities(trim($billing->getFirstname()),ENT_QUOTES,'UTF-8') . "</ewayCustomerFirstName>";
        $xml .= "<ewayCustomerLastName>" . htmlentities(trim($billing->getLastname()),ENT_QUOTES,'UTF-8') . "</ewayCustomerLastName>";
        $xml .= "<ewayCustomerEmail>" . htmlentities(trim($payment->getOrder()->getCustomerEmail()),ENT_QUOTES,'UTF-8') . "</ewayCustomerEmail>";
        $xml .= "<ewayCustomerAddress>" . htmlentities(trim($formatedAddress),ENT_QUOTES,'UTF-8') . "</ewayCustomerAddress>";
        $xml .= "<ewayCustomerPostcode>" . htmlentities(trim($billing->getPostcode()),ENT_QUOTES,'UTF-8') . "</ewayCustomerPostcode>";
//        $xml .= "<ewayCustomerInvoiceRef>" . $this->getQuote()->getReservedOrderId() . "</ewayCustomerInvoiceRef>";
        $xml .= "<ewayCustomerInvoiceRef>" . '' . "</ewayCustomerInvoiceRef>";

It now works as expected, which is great!

1 other questions for you: Why did you not include the Magento Order ID in the XML - see commented line out above. I was wondering why no order ID was visible in the eWay admin earlier as well. Was it causing bugs, and do you see any reason why i could not uncomment it so i can have the corresponding order in eWay for reference?

thanks again!

]]> 2008-07-03T22:15:48-08:00