|
John Ballment
|
August 4, 2015 at 10:53 pm
I original raised this issue with Mandrill and Brett from Mandrill Support came back with the following:
Thanks for getting back to us! Although we’re also seeing those blank pages in your account when looking at the “View Content” links, it (fortunately) appears that we’re not currently seeing any issues with the “View Content” feature within Mandrill.
Instead, this looks to be an issue with the actual HTML content that’s being passed in these messages, which isn’t validating successfully. We were able to test with this same content in our own testing accounts, and received a blank email. For example:
<?\n<!DOCTYPE html PUBLIC \”-//W3C//DTD XHTML 1.0 Transitional//EN\” \”http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\”>\n<html xmlns=\”http://www.w3.org/1999/xhtml\” style=\”margin: 0; padding: 0; font-family: ‘Helvetica Neue’, ‘Helvetica’, Helvetica, Arial, sans-serif;\”>\n <head style=\”margin: 0; padding: 0; font-family: ‘Helvetica Neue’, ‘Helvetica’, Helvetica, Arial, sans-serif;\”>\n<!– If you delete this meta tag, Half Life 3 will never be released. –>\n <meta name=\”viewport\”…..
This HTML is failing to validate due to an unnecessary string at the beginning – <? – which is causing some problems. This is the PHP identifier tag, and therefore the HTML content isn’t being correctly parsed. In our testing, removing those leading characters resulted in a successfully rendered email (and the ability to “View Content”.
|
|
John Ballment
|
August 4, 2015 at 10:56 pm
BTW this has been happening for a while but I upgraded to Version 4.7.9.p yesterday and it has the same problem.
|
|
Tony
|
August 5, 2015 at 7:05 am
Hi John,
Thank you for reporting this, I can confirm the same results on one of my test sites and have created a ticket for our developers to investigate.
We will update this thread with any news.
|
|
Josh
|
August 11, 2015 at 8:55 am
Hi there,
I want to let you know that the issue with the invalid email content is fixed in Event Espresso 4.7.10.p. It’s available as a 1-click update from your WP > Plugins page.
|
|
John Ballment
|
August 11, 2015 at 8:29 pm
Hi Josh,
I just validated that this is not working as expected in my dev environment and I’m pushing it to prod now.
Thanks for the quick resolution.
Regards
John.
|
|
John Ballment
|
August 11, 2015 at 8:30 pm
Hi Josh,
I can confirm that the fix is working correctly in my dev environment and I’m pushing it to Prod.
Thanks for the quick resolution
Regards
John.
|
