How to fix Bonjour {firstname} {lastname}

[samz]

How to fix

Bonjour {firstname} {lastname}

Thank you in advance and regards,

[delete-account-pleas]

Provide me the following files located here:

'yourstore\mails\en\order_conf.html'
and
'yourstore\mails\fr\order_conf.html
 

[samz]

Hello

Here are the 2 files

en_order_conf.html fr_order_conf.html

[delete-account-pleas]

@samz These files are correct.

Can you show the same files but from your theme directory yourstore\themes\classic\mails\fr\order_conf.html

[samz]

I dont have this folder: \themes\classic\mails

[delete-account-pleas]

Hey,

You can find a bug-fix here:

 

[Steve Lorenzo]

On 10/5/2020 at 10:50 PM, Crezzur said:

Hey,

You can find a bug-fix here:

 

I don't think that bug-fix works to fix all the cases such error appears. 

I have the same errors and I don't have users with emails written in ALL CAPS (as that post mentioned above implies as being the bug). 

I'm interested to see a solution to this if someone can chime in, please? 

LATER EDIT ... I checked more thoroughly again, indeed the issue was with the capital letters anywhere in the domain part of the address. 

Thank you @Crezzur

Edited October 30, 2020 by Steve Lorenzo
tested more, found results (see edit history)

[samz]

In my case, this problem appears when the typed email is not all lowercase.

This JAVASCRIPT trims and converts to lowercase the value of all email type INPUT when the focus leaves the field. So it should fix this problem:

String.prototype.trim=function(){return(this.replace(/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,""));}

var mailA=document.querySelectorAll("input[type=email]");
for(var i=0;i<mailA.length;i++){
 mailA[i].onblur=function(){
  this.value=this.value.toLowerCase().trim();
  console.log("["+this.value+"]");
 }
}

Tested OK on PRESTASHOP 1.7.6.8

[samz]

Add this script in this file: /themes/classic/assets/js/custom.js

[chon59]

@samz would this work on 1.7.5.2 ?

 

Thanks

[samz]

@chon069 Sorry, I don't know, I tested my JS script only on PS 1.7.6.8

It should work if this is the same bug on 1.7.5.2

Thanks and regards