[rt-users] Forward template broken in 3.8.6+

[Kevin Falcone]

On Fri, Jun 04, 2010 at 12:46:29PM -0400, Jerrad Pierce wrote:
> Does RT no longer respect the forward template? I had one from 3.8.2,
> and I seem to recall it working fine.

3.8.6 added a second template, one for forwarding Tickets and one for
forwarding just a transaction.

-kevin

> Ours is pretty basic, just a (fairly obvious) note telling people to
> ignore what they don't understand, since
> forwards are generally to those not using the system, and some people
> freak out when they get a message
> with unfamiliar terminology, etc. Today I was trying to amend it to
> include the requestor's email address
> (again, recipients are not int he system, and the attached
> transactions omit this!)
> 
>   Content-Type: text/plain; charset=ISO-8859-1
>   Content-Transfer-Encoding: 7bit
>   Content-Disposition: inline
>   RT-Attach-Message: yes
>   X-Template: Custom
> 
>   This message has been forwarded from CEA ticket #{ $Ticket->id },
> transaction #{ $Transaction->id }.
>   Don't worry if you do not know what this means, simply enjoy the
> message below from { $Ticket->RequestorAddresses }
> 
> But whether I forward a transaction or whole ticket, neither the
> custom header nor the body is included...
> -- 
> Cambridge Energy Alliance: Save money. Save the planet.
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20100604/dcdcfdae/attachment.sig>