Roundcube Community Forum

Release Support => Pending Issues => Topic started by: bobpullen on September 12, 2019, 12:51:04 PM

Title: HTML emails are blank?
Post by: bobpullen on September 12, 2019, 12:51:04 PM
Hi all,

Looking for a bit of guidance on how to troubleshoot this one as I'm out of ideas.

Fresh install of 1.4-rc1 and almost everything seems to be working OK, however whenever I click an HTML email in the message list, all that is displayed in the body of the message in the preview pane is a blank white frame. If I view the message source, it's all there an intact, and if I elect to display all messages in plain text I can see the raw HTML. I can't see anything of relevance in any of the Apache logs but when I check the developer console in a browser, I can see some CSS errors starting with...

Code: [Select]
Source map error: request failed with status 404
Resource URL: https://domain.tld/skins/elastic/deps/bootstrap.min.css?s=1550069270
Source Map URL: bootstrap.min.css.map

Not sure if that's a red herring or not though.

Any ideas on where I can start looking with this one? It happens whether I'm using the elastic or larry skin.

TIA.

Edit: Seems that some HTML emails do actually render, minus images though. Looks like some sort of problem displaying image content  ???
Title: Re: HTML emails are blank?
Post by: bobpullen on September 13, 2019, 08:32:49 AM
So, on closer inspection, it seems that the browser is electing to ignore HTML content entirely:-

(https://res.cloudinary.com/dibpj53fm/image/upload/v1568377887/roundcube_html_problem.jpg)

Anyone seen this before? If I view source, copy the output to a text file, save and reopen it, then the HTML renders perfectly fine.
Title: Re: HTML emails are blank?
Post by: bobpullen on September 13, 2019, 08:47:25 AM
Fixed it.

I'd (roughly) followed the installation guide here (https://www.digitalocean.com/community/tutorials/how-to-install-your-own-webmail-client-with-roundcube-on-ubuntu-16-04), where it (incorrectly) suggests enabling a handful of PHP extensions:-

Quote
Then add extension=dom.so to the bottom of the extension block.

Removing this resolved the issue. FWIW, the two .dll extensions shouldn't be enabled either.