Thank you, I installed this extension and now it works.
Best regards
Bernhard
Von: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] Im Auftrag von
Joop
Gesendet: Freitag, 8. August 2014 08:17
An: rt-users@lists.bestpractical.com
Betreff: Re: [rt-users] Problems with Table in mail
On 8
On 8-8-2014 8:02, Alex Peters wrote:
> RT aggressively sanitises HTML when displaying ticket content to
> prevent some security issues (like a specially crafted HTML attachment
> masquerading as part of the RT interface).
>
> As of RT v4.2.6 onwards, tables will be shown if the HTML::Gumbo Perl
> m
RT aggressively sanitises HTML when displaying ticket content to prevent
some security issues (like a specially crafted HTML attachment masquerading
as part of the RT interface).
As of RT v4.2.6 onwards, tables will be shown if the HTML::Gumbo Perl
module is installed.
On 8 August 2014 15:56, Ei
Hello,
I'm having problems with tables inside of mails.
When someone sends a mail with table to create a new ticket, in the history of
the ticket I cannot see the table, I only see every cell under each other.
When I click on answer- or comment-button, in the new mail the commented table
is sho
I suspect that you'd achieve the functionality you require by bumping these
users up to Privileged and giving them access to the full RT web interface
rather than the Self Service mode.
The full interface can still be quite locked down for some users by
limiting their rights.
Is there any particu
On Thu, Aug 7, 2014 at 2:00 PM, Michael Mol wrote:
[snip]
> ### Begin snippet
> # Find the message from transactionobj->content
> # Set the subject to the message by using ticketobj->SetSubject
>
> my $body = $self->TransactionObj->Content;
> my @lines = split(m/\n/, $body);
> my $trapID = $line
On Thu, Aug 7, 2014 at 12:39 PM, Kevin Falcone
wrote:
> On Fri, Aug 08, 2014 at 01:00:16AM +1000, Alex Peters wrote:
>> I wonder whether both moving the subject-renaming scrip to execute first, and
>> modifying the emailing scrip to run at the "batch" stage might solve your
>> problem.
>
> While
On Fri, Aug 08, 2014 at 01:00:16AM +1000, Alex Peters wrote:
> I wonder whether both moving the subject-renaming scrip to execute first, and
> Â modifying the emailing scrip to run at the "batch" stage might solve your
> problem.
While it's possible to alter the Autoreply template to fetch the newe
Actually, I'm second-guessing my (untested) advice now because I suspect
that both scrips would run on the initial transaction—that is, the emailing
scrip might not necessarily pick up on the subject change because that
would be a different transaction.
I wonder whether both moving the subject-ren
You can adjust the order in which scrips run by moving them up and down in
the list.
I'm guessing that both scrips have the "on create" condition. Simply swap
their order on the queue's Scrips page (or the global one if necessary),
and I believe everything should work as you expect.
On 7 August
So I have a scrip which runs at at the TransactionCreate stage for a
queue, checks the subject and the body, and then rewrites the subject
to something informative.
It works; when I look at the ticket for inbound emails matching the
condition, the subject is precisely what I want it to be.
Except
Hi Kevin,
I managed to mirror the behaviour of the approvals queue by doing exactly
what you said. You are right though, it is awful and horrid.
Thankfully there is a workaround.
Thank you
--
View this message in context:
http://requesttracker.8502.n7.nabble.com/An-Approval-Queue-Problem-tp
12 matches
Mail list logo
