RT 4.0.3 - Email templates are not parsed

Hi

I believe this is the same issue reported by Francesc Guasch
frankie@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.

Thanks for any suggestions,
Jim Berry

Hi

I believe this is the same issue reported by Francesc Guasch frankie@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?

-kevin

Hi

I believe this is the same issue reported by Francesc Guasch frankie@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.

-kevin

Hi

I believe this is the same issue reported by Francesc Guasch frankie@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

Al 10/11/11 22:46, En/na Kevin Falcone ha escrit:> 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@frb.gov wrote:

Hi

I believe this is the same issue reported by  Francesc Guasch<frankie@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.

As 4.0.4 is available, please upgrade it to fix this issue.
Thanks for the report and the extra information.

Great, now it works. Thank you very much for the quick response.