[rt-users] RT 4.0.3 - Email templates are not parsed
Kevin Falcone
falcone at bestpractical.com
Thu Nov 10 16:46:45 EST 2011
On Thu, Nov 10, 2011 at 02:28:30PM -0500, Kevin Falcone wrote:
> On Thu, Nov 10, 2011 at 02:04:42PM -0500, Kevin Falcone wrote:
> > On Thu, Nov 10, 2011 at 01:46:40PM -0500, Jim.H.Berry at frb.gov wrote:
> > > Hi
> > >
> > > I believe this is the same issue reported by Francesc Guasch <frankie at telecos.upc.edu>. We
> > > upgraded from 3.8.10 to 4.0.3. Email is sent as expected via our scrip, but our template is
> > > not parsed, so that we see {$Ticket->Subject}. Earlier I had upgraded from 3.8.10 to 4.0.2
> > > but did have this issue.
> > >
> > > The logs show: [warning]: Use of uninitialized value in string eq at
> > > rt4/sbin/../lib/RT/Template.pm line 410. which is
> > >
> > > if ($self->Type eq 'Perl') {
> > > return $self->_ParseContentPerl(
> > > ...
> > >
> > > Could it be that $self->Type is not getting set? When looking at the template thru the admin
> > > interface, the Type: Perl radio button is checked.
> >
> > If you look in the DB, is the Type field on Templates set?
>
> We've replicated this. For you and Francesco, you can flip the
> Type field in the DB. I expect 4.0.4 to ship soon.
As 4.0.4 is available, please upgrade it to fix this issue.
Thanks for the report and the extra information.
-kevin
-------------- 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/20111110/c50e565c/attachment.sig>
More information about the rt-users
mailing list