Hi.
After upgrade from RT 3.6.6 to RT 4.0.1 all HTML e-mail are not visualized
inline in webinterface.
In out RT_SiteConfig.pm there are
Set( $PreferRichText, 1);
Set( $TrustHTMLAttachments, 1);
Are there some other directives to use?
Luca Villani - Register.It S.p.A. - Dada Group
Tel: +39 055 20021517 Mobile: +39 335 8753086
ICQ: 76272621 Skype: luca.villani
After upgrade from RT 3.6.6 to RT 4.0.1 all HTML e-mail are not visualized
inline in webinterface.
You’re going to have to be more specific as to what’s not showing up.
Screenshots would be useful, for example.
Set( $TrustHTMLAttachments, 1);
This option doesn’t affect display in the normal ticket history page,
only when you the “download” link next to the transaction. Setting
TrustHTMLAttachments to 1 is a serious security risk, and we recommend
leaving it disabled unless you actually understand the full implications.
Thomas
In data venerdì 5 agosto 2011 15:08:19, Thomas Sibley ha scritto:
After upgrade from RT 3.6.6 to RT 4.0.1 all HTML e-mail are not
visualized inline in webinterface.You’re going to have to be more specific as to what’s not showing up.
Screenshots would be useful, for example.
OK, inline visualization looks like Schermata1.png, and when we click on
“Download” visualization looks like Schermata2.png.
In RT 3.6.6 the Schermata2.png we see Schermata2.png visualization inline in
ticket.
Set( $TrustHTMLAttachments, 1);This option doesn’t affect display in the normal ticket history page,
only when you the “download” link next to the transaction. Setting
TrustHTMLAttachments to 1 is a serious security risk, and we recommend
leaving it disabled unless you actually understand the full implications.
We understand full implications, but is the only way to see something useful.
And as far as this is an internal tracker (not the one used for CRM) we can
enable it.
Luca Villani - Register.It S.p.A. - Dada Group
Tel: +39 055 20021517 Mobile: +39 335 8753086
ICQ: 76272621 Skype: luca.villani
OK, inline visualization looks like Schermata1.png, and when we click on
“Download” visualization looks like Schermata2.png.
Ah, much more clear. For security, RT only allows certain HTML when
displaying content inline with the ticket history. What you’re seeing
is that RT has stripped the tables from your message for inline display.
There are answers in the list archives and maybe the wiki for how to
modify ScrubHTML to allow tables inline, although that code has changed
a little from 3.8 → 4.0.
Thomas
In data venerdì 5 agosto 2011 17:03:17, Thomas Sibley ha scritto:
There are answers in the list archives and maybe the wiki for how to
modify ScrubHTML to allow tables inline, although that code has changed
a little from 3.8 → 4.0.
Ok, with a modified
local/html/Elements/ScrubHTML
visualization is useful.
Thank you very much.
Now I’m waiting some hints for our others questions, TMPDIR and inline images
visualizazione… 
Luca Villani - Register.It S.p.A. - Dada Group
Tel: +39 055 20021517 Mobile: +39 335 8753086
ICQ: 76272621 Skype: luca.villani
Ah, much more clear. For security, RT only allows certain HTML when
displaying content inline with the ticket history. What you’re seeing
is that RT has stripped the tables from your message for inline display.
There are answers in the list archives and maybe the wiki for how to
modify ScrubHTML to allow tables inline, although that code has changed
a little from 3.8 → 4.0.Thomas
By the way is there any reason why RT doesn’t allow by default HTML
table elements?
-Chris
Am 05.08.2011 17:03, schrieb Thomas Sibley:
Ah, much more clear. For security, RT only allows certain HTML when
displaying content inline with the ticket history. What you’re seeing
is that RT has stripped the tables from your message for inline display.
There are answers in the list archives and maybe the wiki for how to
modify ScrubHTML to allow tables inline, although that code has changed
a little from 3.8 → 4.0.By the way is there any reason why RT doesn’t allow by default HTML
table elements?
It becomes really trivial to fake ticket history unless we’re really
careful. The real solution is not the scrubber, but something that
actually parses the html mail.
-kevin