dhobo Posted July 15, 2013 Share Posted July 15, 2013 (edited) Hi all, I've installed the Ogone module on my shop, it all works perfectly; I can create orders, pay them with Ogone and get succesfully feedback. When I come back on my shop it even shows me that my order is finished, and in the backend it shows me that the payment for the order is accepted. So all is okay, with only one detail; the client doesn't receive any confirmation email from Prestashop. When I order again, but then choose for a different payment method, such as pay on delivery, then I do get a confirmation email. Does anyone know why via Ogone I don't get any email confirmation ? Edited July 18, 2013 by dhobo (see edit history) Link to comment Share on other sites More sharing options...
tomerg3 Posted July 15, 2013 Share Posted July 15, 2013 Does the order with Ogone finish successfully? Do you get redirected to the order-successful page? Link to comment Share on other sites More sharing options...
dhobo Posted July 16, 2013 Author Share Posted July 16, 2013 yes, it does. I got the order-succesful page and in backend it says that payment is accepted Link to comment Share on other sites More sharing options...
tomerg3 Posted July 16, 2013 Share Posted July 16, 2013 Very very odd, does the order in the backoffice seem valid, IE does it show all the products in the order? The code that sends the customer the confirmation email is in a Prestashop core function, and unless the Ogone module is completely bypassing that funtion (ValidateOrder() in PaymentModule class), it should behave just like the other modules that do send the email. Link to comment Share on other sites More sharing options...
dhobo Posted July 17, 2013 Author Share Posted July 17, 2013 Yes, it all looks completely fine. I found in the code as well that this validateOrder() in PaymentModule is being called in the Ogone module, so it's a very interesting bug that's coming up. Link to comment Share on other sites More sharing options...
dhobo Posted July 18, 2013 Author Share Posted July 18, 2013 Turns out it was a bug in Prestashop core code (http://forge.prestashop.com/browse/PNM-635 ) is fixed now. Link to comment Share on other sites More sharing options...
Recommended Posts