Corrupted emails

  • Resolved carryoncoding

    (@carryoncoding)


    2 years, 2 months ago

    Hi,
    My notification emails have become corrupted pretty much just as the new plugin update (1.9) was installed.

    Originally, the header of the email was setup like this:

    <!DOCTYPE html>
<html lang="en" xmlns="https://www.w3.org/1999/xhtml" xmlns:o="urn:schemas-microsoft-com:office:office">
    <head>
        <meta charset="UTF-8">
        <meta name="viewport" content="width=device-width,initial-scale=1">
        <meta name="x-apple-disable-message-reformatting">
        <title></title>
        <!--[if mso]>
            <noscript>
                <xml>
                <o:OfficeDocumentSettings>
                <o:PixelsPerInch>96</o:PixelsPerInch>
                </o:OfficeDocumentSettings>
                </xml>
            </noscript>
        <![endif]-->
        <style>
            .email-button {

    But after the update, the notification message body is full of blank lines and looks like this:

        
        
        
        
        <title></title>
        <!--[if mso]>-->
            
                
                
                96
                
                
            
        
        
            .email-button {

    I tried pasting the code back into the message body box, saved it, tried a test, and the code was deleted again.
    Please can you help?
    Thanks,
    Phil.

Viewing 15 replies - 1 through 15 (of 25 total)
  • Plugin Author bnfw

    (@voltronik)

    Hi @carryoncoding,
    Thanks for your message.

    Can you please send me the all of the code you’re using in your email via a link so I can test this myself?

    Thread Starter carryoncoding

    (@carryoncoding)

    Thanks. The code is now corrupted but I can extract it from an earlier, successful email.

    What mechanism do you mean by “via a link”?
    Cheers,
    Phil.

    Plugin Author bnfw

    (@voltronik)

    Hi @carryoncoding,
    Ok, thanks.

    If you can post a link to the code, e.g. a Gist, then I can go there to download it rather than pasting a long HTML email which may get sanitised, here.

    Thread Starter carryoncoding

    (@carryoncoding)

    Please see the following gist. It includes a pieced-together version of the correct code, followed by a copy of the corrupted code.

    https://gist.github.com/Phil-Avalon/115ef24d086d6f5929f5b92d095d8b42

    Plugin Author bnfw

    (@voltronik)

    Thanks @carryoncoding,
    I’ve been able to confirm the bug and will look to release an update to fix this as soon as it’s ready.

    Thread Starter carryoncoding

    (@carryoncoding)

    ??

    Thread Starter carryoncoding

    (@carryoncoding)

    Just checking into see what progress there is on this.
    Thanks,
    Phil.

    Plugin Author bnfw

    (@voltronik)

    Hi @carryoncoding,

    Yes, this is currently being worked on and should be released as part of the next update.

    Thread Starter carryoncoding

    (@carryoncoding)

    Many thanks.

    Thread Starter carryoncoding

    (@carryoncoding)

    Hi, just checking in for an update on progress. Problem still exists in ver 1.9.1.

    Many thanks,
    Phil.

    Plugin Author bnfw

    (@voltronik)

    Hi @carryoncoding,

    No update just yet. It’s part of a few larger updates that I want to release at the same time.
    It appears that not all code will be allowed in an email as WordPress’s wp_mail() function, which BNFW has to use to send notifications out as emails, strips some tags. An example of this is the <!--[if mso]>--> you have in your email.
    Just a heads-up in case you need to change this after the update comes out.

    Thread Starter carryoncoding

    (@carryoncoding)

    Thanks very much for this response.

    I have tried removing the Lines:

    <!--[if mso]>
<noscript>
<xml>
<o:OfficeDocumentSettings>
<o:PixelsPerInch>96</o:PixelsPerInch>
</o:OfficeDocumentSettings>
</xml>
</noscript>
<![endif]-->

    but when I click “save”, the notification message body continues to be corrupted.
    Have you any other thoughts what might be causing this?
    Thanks,
    Phil.

    Plugin Author bnfw

    (@voltronik)

    Hi @carryoncoding,
    Apologies, to clarify: you’ll still need to wait for the update for BNFW to come out but it was just a heads up that some of your code won’t work with any email in WordPress so you may wish to change this or test it when the update is out.

    Hope this makes sense but just let me know if not.

    Thread Starter carryoncoding

    (@carryoncoding)

    OK, thanks.

    Looking forward to the update!
    Kind regards,
    Phil.

    Thread Starter carryoncoding

    (@carryoncoding)

    Hi again, just checking in to see how things are progressing. Do we have a release date for the fix yet?

    Many thanks,

    Phil.

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Corrupted emails’ is closed to new replies.