-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
html not rendering in roundcube #5957
Comments
Are you talking about mail preview or composing? Any errors in log? Any errors in javascript console? Did you try with disabled all plugins? Did you try with different browser? What browser? |
->mail preview i used all the plugins originally, but then I disabled all of them, same result. in firefox, under the browser console (JS) this error consistently pops up: In the error log for roundcube... nothing shows up at all, except for the early errors while establishing the service, i page through the emails in preview of the html code, nothing pops up under tail -f ./errors log is set to 1 or 4, same result (defaults). I imagine that there is a process where the code is flipped from text to code inside the pane, but it's not happening. Any suggestions are welcome. It's been a while since i trouble-shot j/s & html5. not terribly interested, but if i get a clue/direction I can try. |
well this fixed it, ... please acknowledge, probably needs to be considered in the next roll out.
(replace all?) |
That's interesting. DOMElement has tagName property defined, but DOMNode does not. Still I have no idea why that does not work for you. |
…stems (#5957) Consistently use $nodeName instead of $tagName property.
…stems (#5957) Consistently use $nodeName instead of $tagName property.
…stems (#5957) Consistently use $nodeName instead of $tagName property.
Fixed. |
system - ubuntu 16.04
php - 7.0.22-0ubuntu0.16.04.1
it's a very straightforward install, no real fancy stuff, but it is not working out of the box, i get basically the 'code' not a rendering of the html.
the release indicated by the CHANGELOG is 1.3.1
*plain text works fine
The text was updated successfully, but these errors were encountered: