WooCommerce Emails HTML Broken

@danielrufde It works! Wonderful, thank you so much Daniel!

UPDATE: I see Blacknight and other users have already noticed this fix. https://www.ads-software.com/support/topic/woocommerce-emails-html-broken/page/3/#post-12590031

I had this problem too on a number of sites. All are hosted on Blacknight shared.

I spent over 2 hours on chat with WooCommerce support but could not solve the problem.

I used the WordPress Health Check & Troubleshooting plugin to disable all plugins bar WooCommerce and switched to a default theme, yet the problem persisted.

The problem seems to be an incompatibility with WooCommerce 4 and the PHP Mailer.

I got around the problem by using an SMTP plugin (WP Mail SMTP Lite), selecting Other SMTP in the settings and entering credentials for an existing mailbox on this hosting.

• This reply was modified 4 years, 8 months ago by Jim Daly. Reason: Fix already discovered

@glicit see https://www.ads-software.com/support/topic/woocommerce-emails-html-broken/page/3/#post-12604442

Basically the email contains a string which is too long for valid emails. Your solution is merely a workaround than a solution as it bypasses the problem when a different library parses the email content.

But be aware that also other libraries to send emails may apply such restrictions on the maximum line length in the future and then you have the same issue again.

And some email providers may reject or cause issues too in the case when there is a string / line which is too long.

@danielrufde Thanks for this. It’s a far superior solution.

Hi @danielrufde ,

thanks for this tip, unfortunately it did not work for me. I still have the code in my emails. for example, my mail starts like this:

< td align=”center” valign=”top”>

….

@genialeregale please check the sourcecode of the email in your email client. You can temporarily disable the max-length check in wp-includes/class-phpmailer.php to check easier which long line might trigger this in your case.

Also ensure that the code is added to the correct functions.php (of your currently used WordPress theme).

See https://www.ads-software.com/support/topic/woocommerce-emails-html-broken/page/3/#post-12588237

So one of the following might allow the output of the unshortened content:

if (‘base64’ != $this->Encoding and self::hasLineLongerThanMax($this->Body)) {
// $bodyEncoding = ‘quoted-printable’;
}

//if (‘base64’ != $this->Encoding and self::hasLineLongerThanMax($this->Body)) {
// $bodyEncoding = ‘quoted-printable’;
//}

@danielrufde I was having the same problem that everyone else had. I am so glad 1 friend on Instagram reached out to my IG story asking for help and he linked me to Page 3 of this thread. THANK YOU SO MUCH!!!! You prevented more headaches of hours and hours of extra reading and research in addition to previous hours. I hope you are getting paid well where ever you work.

Ivee

@danielrufde thank you so much, it works! Finally I can get back to normal business :)!

One question though, can this code be left in the functions.php now forever or will i have to remove it at some point in time?

@danibanani88 the code can be left there, until this may be fixed. See also https://github.com/woocommerce/woocommerce/issues/26015

Not sure if and when this will be fixed.

@danielrufde @gjanezic

Thanks for narrowing down where the problem is and helping us get the emails working again. ur awesome.

@gjanezic @chinaman123 @karinorage @glicit @genialeregale @kerkocivee @danibanani88

See https://github.com/woocommerce/woocommerce/issues/26015#issuecomment-608509272 which contains another snippet that you can use as an alternative temporary solution (I did not test this).

The issue which caused this was found and will be fixed by https://github.com/woocommerce/woocommerce/pull/26075 so you can remove the snippets when this fix will be released.

Thanks @danielrufde for your snippet. It worked perfectly for me.

Thanks @danielrufde. This saved a lot of time. WC support cant replicatie the error, but I’m glad it is not a plugin conflict

Thanks a lot @danielrufde for the snippet.

I had blank emails and the snippet solved it.

I had the same problem, and the code from @danielrufde solved it. Thanks!