Dexter_X Posted October 13, 2021 Posted October 13, 2021 Hi, I've already reported that bug, but it seems not yet solved : the e-mail notifying a transaction is awaiting validation (commerce) does not seem to refer to the right string. The content message is only "email_transaction_wait" instead of the corresponding string content. Please, this affects customers relations because it appears like "bugged" and does not inspires confidence... Thankyou
Jim M Posted October 13, 2021 Posted October 13, 2021 By "awaiting validation" are you referring to the payment being held for manual approval or actual email validation during the process?
Dexter_X Posted October 13, 2021 Author Posted October 13, 2021 I refer to the notification telling a payment is being held. Thankyou
Marc Posted October 14, 2021 Posted October 14, 2021 Please could you check and confirm this is happening on a standard unaltered language pack first of all?
Dexter_X Posted October 14, 2021 Author Posted October 14, 2021 Hi, I've already notified that bug : the problem is the referenced string by the e-mail template email_transaction_wait does not exist, the current right string is email_transaction_waiting.
Dexter_X Posted October 14, 2021 Author Posted October 14, 2021 I'm maybe wrong, it seems not to be in the user's notification but in the administrator's notification, in the e-mail template there is this line : {$email->language->addToStack( "email_transaction_" . $notification->extra, FALSE )} It seems to add "wait" instead of "waiting" or the problem is the email_transaction_wait string is not defined (?)
Marc Posted October 14, 2021 Posted October 14, 2021 Have managed to pinpoint it and added a bug report for this. Im not sure where it was reported previously, but I'm not able to see that report anywhere. Apologies if that has been missed somewhere along the way, but there is a report in there now for it Dexter_X 1
Marc Posted November 10, 2021 Posted November 10, 2021 Just a quick update on this to let you know that a fix has been pushed for this, so it will be in a future release. I will update once that has gone in Dexter_X 1
Solution Marc Posted December 7, 2021 Solution Posted December 7, 2021 This has now been resolved in the 4.6.9 version which has just been released. Please feel free to let us know if you are seeing any issues after upgrading Dexter_X 1
Dexter_X Posted December 9, 2021 Author Posted December 9, 2021 Thankyou, I'll install it on next saturday, so I'll be glad to see it working ! 🙂
Recommended Posts