But when you submit the ticket the inline screenshot goes away. If you click
the download link you get the raw html showing <img alt=“”
src="data:image/png;base64,iVBORw.
Now, if you ATTACH a screenshot, that does show inline.
With all of that said about the demo site, on my clean install of RT 4.0.5,
I can’t even paste the screenshot in.
Is there a way to get inline screenshots working? The kind of problems we
are tracking will require multiple screenshots for the ticket and to have
them have to save each screenshot and attach them would really defeat the
purpose of streamlining the process.
I got this working in RT 3.8.8 with modifying /Elements/SrubHTML to
authorize IMG elements and src attribute. After that you can see
inline images in ticket history.
In RT4, SrubHTML have been moved to /RT/Interface/Web.pm
But when you submit the ticket the inline screenshot goes away. If you click
the download link you get the raw html showing <img alt=“”
src="data:image/png;base64,iVBORw.
Now, if you ATTACH a screenshot, that does show inline.
With all of that said about the demo site, on my clean install of RT 4.0.5,
I can’t even paste the screenshot in.
Is there a way to get inline screenshots working? The kind of problems we
are tracking will require multiple screenshots for the ticket and to have
them have to save each screenshot and attach them would really defeat the
purpose of streamlining the process.
I got this working in RT 3.8.8 with modifying /Elements/SrubHTML to
authorize IMG elements and src attribute. After that you can see
inline images in ticket history.
In RT4, SrubHTML have been moved to /RT/Interface/Web.pm
Does the message need to be formatted as HTML to begin with?
Oh wait, someone else sent an email from Outlook, formatted as HTML, and
it does look like the image link is displayed online then. So I guess
that’s the requirement. RT4 won’t display it inline if the original
email was plain text (which makes sense, duh).
I got this working in RT 3.8.8 with modifying /Elements/SrubHTML to
authorize IMG elements and src attribute. After that you can see
inline images in ticket history.
In RT4, SrubHTML have been moved to /RT/Interface/Web.pm
Does the message need to be formatted as HTML to begin with?
Note that such change introduces security vulnerability that is easily
exploitable. People can insert URLs into img’s src attribute that
point to RT itself and do some actions on behalf of the user who is
looking at the ticket.
I got this working in RT 3.8.8 with modifying /Elements/SrubHTML to
authorize IMG elements and src attribute. After that you can see
inline images in ticket history.
In RT4, SrubHTML have been moved to /RT/Interface/Web.pm
Does the message need to be formatted as HTML to begin with?
Note that such change introduces security vulnerability that is easily
exploitable. People can insert URLs into img’s src attribute that
point to RT itself and do some actions on behalf of the user who is
looking at the ticket.
In my case I tweek a little more the scrubber to avoid (reduce)
security issues,
the only thing I wanted is the ability to paste en image in the
CKeditor (<img src="data:image/png;base64… />)
this do the trick after the $scriubber->allow() call.
In my case I tweek a little more the scrubber to avoid (reduce)
security issues,
the only thing I wanted is the ability to paste en image in the
CKeditor (<img src="data:image/png;base64… />)
this do the trick after the $scriubber->allow() call.
Could you tell us what local variable you mean?
there isn’t the release note for the 4.0.6 in the web page.
Thomas Sibley wrote:
In my case I tweek a little more the scrubber to avoid (reduce)
security issues,
the only thing I wanted is the ability to paste en image in the
CKeditor ( "data:image/png;base64… )
this do the trick after the $scriubber->allow() call.