leoly

Thank you. After more research, it seems the formatting changes might be from the email provider. It might be changing the email it receives from Google, which is then reflected in Postie’s output. Really appreciate your excellent support; I left a review as well.

btw, not sure if you were aware of this already, but Postie and the NextScripts: Social Networks Auto-Poster plugin don’t work well with each other. Nextscripts doesn’t auto-post, posts made by Postie. The Nextscripts developer noted that this is due to how postie publishes posts.

Thanks. Turned off my other plugins to test, and still got the same results.

For some reason, my text editor is showing an extra div around each paragraph, and instead of the <br><br> it's showing as <div><div>?

<div dir=”ltr”>
<div>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.</div>
<div></div>
<div>Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>
</div>

Hello,

Thanks for the prompt response, the test email has been sent.

Having the same issue. Email posts by Postie that are published, are not getting sent to configured social media accounts by NextScripts.

Thank you for the prompt response.

Thank you.

Confirming that the thumbnail height is not resizing properly in Chrome. Used to work well, but something changed recently that is affecting the resizing.

Thanks. It worked.

Same here, were you able to find a solution?

Same here, were you able to find a solution?

Thank you Chris Dillion, your suggestion worked on 4.1.

Is there a way to make the custom post type pages, like they were in the older version of Responsive?

Like before the types were under pages, not posts. Thanks.

Seems the problem is with Super Cache, so we disabled it for now. Thanks for the quick response.

Does anyone have a fix for this problem?