Outlook 2013 rendering challenge

It is possible that it is Word 2013 and not the plugin or Outlook. I really don’t know. I upgraded my office PCs from Office 2007 and Office 2010 to Office 2013. I checked one of my newsletters from June (prior to the upgrades) and even the older ones look wrong now when they looked fine in an older version of Outlook and Word.

It is my understanding that Outlook 2013 uses MS Word 2013 for rendering all HTML in emails. I’ve enabled the “use CSS” checkbox in options, but it is not having any effect.

You can see in this image (https://www.joyfullifechurch.org/wp-content/uploads/2015/07/Mailpoet-Challenges-in-Outlook-2013.jpg) that the text in these tables is not readable.

Any thoughts or guidance?

Follow-up: If I open the email (which looks terrible, as you can see in the image from the previous post) and choose Actions -> View in Browser, Internet Explorer (I prefer Chrome) renders the email newsletter without fail. So the code is being generated properly. But somehow, Outlook/MS Word do not present this content in the desired format.

Can you please send us the link to the View in Browser version so we could check properly what’s going on in the HTML of the email?

Thanks MailPoet team. We greatly appreciate any guidance you can offer. The HTML in the “view in browser” link looks great. Just doesn’t look good in Outlook 2013.

https://www.joyfullifechurch.org/?wysija-page=1&controller=email&action=view&email_id=12&wysijap=subscriptions

Thanks for the link!

Looks like you’ve inserted these HTML tables directly on the Newsletter Editor. MailPoet 2’s parser doesn’t tables by itself. The upcoming MailPoet 3 is supposed to support tables, but not MP2. Therefore we can’t provide support for your HTML code at this moment.

Sorry for that!

What is the timeline for releasing MailPoet 3? Some of the earlier communications from MailPoet indicated it would be coming in early 2015. It’s too late for that now but a target date would be helpful.

Just as importantly, will MP v3 include table support per your note above? We need this capability as soon as possible and would prefer not switching to another plugin to find it. But if version 3 is not going to include this, then we have no other choice but to look for another way to do it.