Callbacks help

We have a tool for RTFM that worked with RT3.0.x but doesnt work with
3.2.x… Ive been told callbacks changed. The Callbacks stuff is in:

/opt/rt/local/html/Callbacks/brokentool/Ticket/Elements/ShowLinks

And this file reads:

<%args>
$Ticket
</%args>

Create new Othertool ticket

If I go in and do it the “wrong” way and edit
/opt/rt/share/html/Elements/ShowLinks and add this, it works:

    Create new Othertool ticket

Tried adding the

    tags to the local callbacks, no luck. Any ideas
    what needs to change? I cant find any documentation.

I think the problem is the path in your Callbacks directory, it should
be in

/opt/rt/local/html/Callbacks/brokentool/Elements/ShowLinks

Not

/opt/rt/local/html/Callbacks/brokentool/Ticket/Elements/ShowLinks

Regards,
Matt.

-----Original Message-----
From: rt-devel-bounces@lists.bestpractical.com [mailto:rt-devel-
bounces@lists.bestpractical.com] On Behalf Of Craig Schenk
Sent: Thursday, March 31, 2005 1:59 AM
To: rt-devel@lists.bestpractical.com
Subject: [Rt-devel] Callbacks help

We have a tool for RTFM that worked with RT3.0.x but doesnt work with
3.2.x… Ive been told callbacks changed. The Callbacks stuff is in:

/opt/rt/local/html/Callbacks/brokentool/Ticket/Elements/ShowLinks

And this file reads:

<%args>
$Ticket
</%args>

<A

HREF="http://url.com/othertool.cgi?action=Create+ticket&related_rt_tick

et= <% $Ticket->Id %>&current_user=<% $session{‘CurrentUser’}->Name |u
%>&description=<% $Ticket->Subject |u %>" >Create new Othertool
ticket

If I go in and do it the “wrong” way and edit
/opt/rt/share/html/Elements/ShowLinks and add this, it works:

Tried adding the

This email and any files transmitted with it are confidential and intended solely for the
use of the individual or entity to whom they are addressed. Please notify the sender
immediately by email if you have received this email by mistake and delete this email
from your system. Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the organisation.
Finally, the recipient should check this email and any attachments for the presence of
viruses. The organisation accepts no liability for any damage caused by any virus
transmitted by this email.