Strange error on give

RT Users
1

RT3

Requestors: Program fragment delivered error ``RT::Group::EmailsAsString
Unimplemented in T. (template line 9)

Stack:
[/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Record.pm:457]
[template:9]
[/opt/rt3/lib/RT/Template_Overlay.pm:389]
[/opt/rt3/lib/RT/Template_Overlay.pm:315]
[/opt/rt3/lib/RT/Action/SendEmail.pm:210]
[/opt/rt3/lib/RT/ScripAction_Overlay.pm:199]
[/opt/rt3/lib/RT/Scrip_Overlay.pm:394]
[/opt/rt3/lib/RT/Scrip_Overlay.pm:337]
[/opt/rt3/lib/RT/Transaction_Overlay.pm:169]
[/opt/rt3/lib/RT/Ticket_Overlay.pm:3799]
[/opt/rt3/lib/RT/Ticket_Overlay.pm:3138]
[/opt/rt3/lib/RT/Interface/Web.pm:1081]
[/opt/rt3/share/html/Ticket/ModifyAll.html:117]
[/opt/rt3/share/html/autohandler:182]’’

Has anyone seen this before?

InteleNet Communications Inc.
Chance Ervin - SCSA
Oracle Certified Professional
Lead NOC Engineer

1

2

My bet is :
Whoever upgraded you from RT2, just copied email templates blindly
without taking API changes into account.

-jOn Sat, Aug 30, 2003 at 11:06:40AM -0700, Chance Ervin wrote:

RT3

Requestors: Program fragment delivered error ``RT::Group::EmailsAsString
Unimplemented in T. (template line 9)

Stack:
[/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Record.pm:457]
[template:9]
[/opt/rt3/lib/RT/Template_Overlay.pm:389]
[/opt/rt3/lib/RT/Template_Overlay.pm:315]
[/opt/rt3/lib/RT/Action/SendEmail.pm:210]
[/opt/rt3/lib/RT/ScripAction_Overlay.pm:199]
[/opt/rt3/lib/RT/Scrip_Overlay.pm:394]
[/opt/rt3/lib/RT/Scrip_Overlay.pm:337]
[/opt/rt3/lib/RT/Transaction_Overlay.pm:169]
[/opt/rt3/lib/RT/Ticket_Overlay.pm:3799]
[/opt/rt3/lib/RT/Ticket_Overlay.pm:3138]
[/opt/rt3/lib/RT/Interface/Web.pm:1081]
[/opt/rt3/share/html/Ticket/ModifyAll.html:117]
[/opt/rt3/share/html/autohandler:182]‘’

Has anyone seen this before?

InteleNet Communications Inc.
Chance Ervin - SCSA
Oracle Certified Professional
Lead NOC Engineer

1

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

3

My bet is :
Whoever upgraded you from RT2, just copied email templates blindly
without taking API changes into account.

I suspect that was me then and relates to the “couldn’t parse head” email I
posted the other day.

This template was copied from rt2. There’s a blank line before “Request #”.
I’m guessing it’s the Requestor that’s causing the error.

Request #{$Ticket->id} has been GIVEN TO YOU on
{$Transaction->CreatedAsString} by {$Transaction->CreatorObj->RealName}.

Transaction: {$Transaction->Description}
Queue: {$Ticket->QueueObj->Name}
given)"}
Owner: {$Ticket->OwnerObj->Name}
Requestors: {$Ticket->Requestors->EmailsAsString()}
Status: {$Ticket->Status}
Ticket <URL: {$RT::WebURL}Ticket/Display.html?id={$Ticket->id} >
{$Transaction->Content()}

4

matthew zeier wrote:

My bet is :
Whoever upgraded you from RT2, just copied email templates blindly
without taking API changes into account.

I suspect that was me then and relates to the “couldn’t parse head” email I
posted the other day.

This template was copied from rt2. There’s a blank line before “Request #”.
I’m guessing it’s the Requestor that’s causing the error.

Request #{$Ticket->id} has been GIVEN TO YOU on
{$Transaction->CreatedAsString} by {$Transaction->CreatorObj->RealName}.

Transaction: {$Transaction->Description}
Queue: {$Ticket->QueueObj->Name}
Subject: {$Transaction->Subject || {$Ticket->Subject} || “(No subject
given)”}
Owner: {$Ticket->OwnerObj->Name}
Requestors: {$Ticket->Requestors->EmailsAsString()}

No more EmailAsString sub. Now it’s MemberEmailAddressesAsString

Requestors: {$Ticket->Requestors->MemberEmailAddressesAsString()}

Good luck. Ruslan.