You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In correct operation Prestashop will – with or without the Mollie plugin – display an order confirmation page to customers returning to the shop from making a payment. Some customers will notice a change here when they use a version of Prestashop ≤ 1.6.0.7 and the Mollie plugin ≥ 1.0.3. The anomaly is that under these circumstances the customers are shown their order-history instead. Not a giant problem, but both unexpected and undesirable.
The text was updated successfully, but these errors were encountered:
This is in fact a bug in Prestashop that was fixed in version 1.6.0.7. It has to do with the OrderConfirmationController that on line 73 checks whether the module matches the payment.
To fix it upgrading Prestashop to ≥ 1.6.0.7 is without a doubt the cleanest solution. However, if you're (temporarily) stuck anywhere between 1.5.x and 1.6.0.6 you could simply edit the code this way:
Find line 72 or 73 (depends on your actual current version) of the file controllers/front/OrderConfirmationController.php which reads:
Hi- I have this issue still where all orders are redirected from Paypal to order history. I desperately need these to fire scripts, have no clue why. My Prestashop is 1.6.1 and website is www.bedandwood.com. I have attached the first data.php file. Order confirm contr.php has ->name as one would expect.
In correct operation Prestashop will – with or without the Mollie plugin – display an order confirmation page to customers returning to the shop from making a payment. Some customers will notice a change here when they use a version of Prestashop ≤ 1.6.0.7 and the Mollie plugin ≥ 1.0.3. The anomaly is that under these circumstances the customers are shown their order-history instead. Not a giant problem, but both unexpected and undesirable.
The text was updated successfully, but these errors were encountered: