Scrip failures

RT Users
#1

When I reply to a ticket in my freshly upgraded RT 2.0.13, it does not send
the reply to the requestor, instead it just says “comments added” vs.
“correspondence sent”. I took a look at my scrips and they are definately
broken. I have the first drop-down box populated with the usual
"OnReply,OnComment,OnResolve, etc…" but the next two boxes for the action
and the templates are missing any entries. Where should I look for my missing
scrips? I know that I was meddling with scrips awhile back but I cannot find
the file(s) that are responsible.

TIA

– RT2 Troubles

#2

Hello,

I’m getting errors in RT 3.8.1 log like:

[Tue Jan 27 02:51:50 2009] [error]: Scrip Commit 6 died. - Can’t call
method "parts"
on an undefined value at /opt/rt3/bin/…/lib/RT/I18N.pm line 196.
Stack:
[/opt/rt3/bin/…/lib/RT/I18N.pm:196]
[/opt/rt3/bin/…/lib/RT/I18N.pm:196]
[/opt/rt3/bin/…/lib/RT/Action/SendEmail.pm:520]
[/opt/rt3/bin/…/lib/RT/Action/SendEmail.pm:141]
[/opt/rt3/bin/…/lib/RT/ScripAction_Overlay.pm:238]
[/opt/rt3/bin/…/lib/RT/Scrip_Overlay.pm:464]
[/opt/rt3/bin/…/lib/RT/Scrips_Overlay.pm:196]
[/opt/rt3/bin/…/lib/RT/Transaction_Overlay.pm:177]
[/opt/rt3/bin/…/lib/RT/Record.pm:1419]
[/opt/rt3/bin/…/lib/RT/Ticket_Overlay.pm:2145]
[/opt/rt3/bin/…/lib/RT/Ticket_Overlay.pm:2057]
[/opt/rt3/bin/…/lib/RT/Interface/Web.pm:705]
[/opt/rt3/share/html/Ticket/Display.html:145]
[/opt/rt3/share/html/Ticket/Update.html:257]
[/opt/rt3/share/html/autohandler:308]
(/opt/rt3/bin/…/lib/RT/Scrip_Overlay.pm:472)

It occurs for both emails, and web interactions, and seems to be related to
Transaction->Content not being included in notifications. Below is the current
template being used for #6 (Admin Comment). Essentially the same code is
being used for #5 (Admin Correspondence) and #3 (Transaction). There is no
error log entry for #3, but none of them include the message body :-/
Any help would be greatly appreciated.

$s =~ s/[Comment]//g; $s =~ s/^Re//i; $s;}
X-Priority: {my $p=$Ticket->Priority; $p=50 if $p<0; 6-(int(($p/20)+.5)||1)}

This is a comment. It is not sent to the Requestor(s):

<URL: {RT->Config->Get(‘WebURL’)}Ticket/Display.html?id={$Ticket->id} >
{ #Link to attachments
my @res;
my $Attachments = $Transaction->Attachments;
$Attachments->Limit( FIELD => ‘Filename’, OPERATOR => ‘!=’, VALUE => ‘’ );
while (my $a = $Attachments->Next) {
push(@res, sprintf("%sTicket/Attachment/%i/%i/%s", $RT::WebURL,
$a->TransactionId, $a->id, $a->Filename));
}
@res ? join(’’, map{ “<enc: $_ >\n” } @res ) : ‘’;
}

{$Transaction->Content()}

#3

Okay, still no idea what’s causing the commit failure,
but I have determined that the attachment link code
(adapted form wiki content) somehow results in an
empty Transaction->Content. Is the Limit not scoped?
Cambridge Energy Alliance: Save money. Save the planet.

#4

Jerrad,

The limit for attachments is set in the RT_SiteConfig.pm file in

$RTHOME->etc directory.

Kenn
LBNLOn 1/27/2009 10:15 AM, Jerrad Pierce wrote:

Okay, still no idea what’s causing the commit failure,
but I have determined that the attachment link code
(adapted form wiki content) somehow results in an
empty Transaction->Content. Is the Limit not scoped?

#5

Jerrad,

   The limit for attachments is set in the RT_SiteConfig.pm file in

$RTHOME->etc directory.
Hi Ken, I think you may have misunderstood. I was not referring to attachment
size limit, but the ->Limit() method call in the previously quoted code.

Cambridge Energy Alliance: Save money. Save the planet.

#6

Okay, further details of this very very bad thing. The templates are
not the problem,
“On Correspond Notify Requestors and CCs” is croaking for responses submitted
via the web interface.

I rechecked the ScripActions table, since I added "Notify AdminCCs and Owners"
last night, but this looks right to me:

id | Name | Description | ExecModule | Argument | Creator
6 | Notify Ccs | Sends mail to the Ccs | Notify | Cc | 1

It seems very odd that internationalization should be capable of
inducing message
delivery failure…
Cambridge Energy Alliance: Save money. Save the planet.