Wrong Variable Substitution in Template

Hello,

in a new RT installation, I have the following problem:

I have created a Scrip (OnResolve NotifyRequestor Resolved-deu).
Now, if the Template includes the Ticket Subject via
{$Transaction->Subject || {$Ticket->Subject} || “(No subject given)”},
as in the Transaction template, the system substitutes this wit
HASH(0Xxxxxxx) instead of the Subject (which is reflected correclty in
the Mail’s subject, by the way).

Obviously, I’ve broken something. I would be thankful if someone had an
idea how to fix this and would like to share it.

Regards,
Harald
Harald Wagener | Systemadministrator
FCB/Wilkens GmbH | Tel.:+49-40-2881-1252
An der Alster 42 | Fax.:+49-40-2881-1263
20099 Hamburg | http://www.fcb-wilkens.com

I have created a Scrip (OnResolve NotifyRequestor Resolved-deu).
Now, if the Template includes the Ticket Subject via
{$Transaction->Subject || {$Ticket->Subject} || “(No subject given)”},

Try:

{ $Transaction->Subject || $Ticket->Subject || “(No subject given)” }

The ‘{’ and ‘}’ characters in the templates define code escapes, and
terminating one prematurely is bad juju :wink:

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

Bruce Campbell wrote:

I have created a Scrip (OnResolve NotifyRequestor Resolved-deu).
Now, if the Template includes the Ticket Subject via
{$Transaction->Subject || {$Ticket->Subject} || “(No subject given)”},

Try:

{ $Transaction->Subject || $Ticket->Subject || “(No subject given)” }

The ‘{’ and ‘}’ characters in the templates define code escapes, and
terminating one prematurely is bad juju :wink:

Regards,

Thanks Bruce. But in RT 2.0.11 the braces around $Ticket->Subject are
standard in the Transaction Template, so this might be an error in the
distribution. Unfortunately I cannot test if Your correction Does It™
for me, because the mail feature broke[1] while I moved from home to
work )-:

Regards,
Harald

[1] a.k.a. 'I dinna change no thing!'
Harald Wagener | Systemadministrator
FCB/Wilkens GmbH | Tel.:+49-40-2881-1252
An der Alster 42 | Fax.:+49-40-2881-1263
20099 Hamburg | http://www.fcb-wilkens.com

Thanks Bruce. But in RT 2.0.11 the braces around $Ticket->Subject are
standard in the Transaction Template, so this might be an error in the
distribution. Unfortunately I cannot test if Your correction Does It™

Ah. Revision 1.4 of rt/tools/insertdata has the erronous '{}'s in the
Transaction Template, but Revision 1.5 has the corrected version.
Unfortunately™, 1.4 is tagged as rt-2-0-11.

Your fun bash one-liner for the moment is:

prev="" ; for rev in `cvs log insertdata | grep ^revision | cut -d
' ' -f 2` ; do if [ "$prev" -a "$rev" ] ; then echo "$rev ->
$prev" ; cvs diff -r$rev -r$prev insertdata ; fi ; prev="$rev" ;
done | less

Regards,

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

Bruce Campbell wrote:

[snip]

Ah. Revision 1.4 of rt/tools/insertdata has the erronous '{}'s in the
Transaction Template, but Revision 1.5 has the corrected version.
Unfortunately™, 1.4 is tagged as rt-2-0-11.

Thank You!

Your fun bash one-liner for the moment is:

    prev="" ; for rev in `cvs log insertdata | grep ^revision | cut -d
    ' ' -f 2` ; do if [ "$prev" -a "$rev" ] ; then echo "$rev ->
    $prev" ; cvs diff -r$rev -r$prev insertdata ; fi ; prev="$rev" ;
    done | less

To call this a one liner might be a stretch of reality (-: . I assume I
should have cvs set up correctly before trying this, yes?

Regards,
Harald

Harald Wagener | Systemadministrator
FCB/Wilkens GmbH | Tel.:+49-40-2881-1252
An der Alster 42 | Fax.:+49-40-2881-1263
20099 Hamburg | http://www.fcb-wilkens.com

Thank You!

Your fun bash one-liner for the moment is:

    prev="" ; for rev in `cvs log insertdata | grep ^revision | cut -d
    ' ' -f 2` ; do if [ "$prev" -a "$rev" ] ; then echo "$rev ->
    $prev" ; cvs diff -r$rev -r$prev insertdata ; fi ; prev="$rev" ;
    done | less

To call this a one liner might be a stretch of reality (-: . I assume I
should have cvs set up correctly before trying this, yes?

urm, no, it was just my little quick script to check my local copy of the
RT CVS tree for where the error crept in. Apart from that, it has no
relevance on your problem.

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations