Transaction_Overlay.pm problem?

I am trying to upgrade from 3.0.8 to 3.6.1 and am seeing this message in
the rt.log:

Use of uninitialized value in pattern match (m//) at
/opt/rt/lib/RT/Transaction_Overlay.pm line 1073

The bit that it seems to complain about is:

sub CustomFieldValues {
my $self = shift;
my $field = shift;

 if ( UNIVERSAL::can( $self->Object, 'QueueObj' ) ) {

=============> unless ( $field =~ /^\d+$/o ) { <===============

         my $CFs = RT::CustomFields->new( $self->CurrentUser );
          $CFs->Limit( FIELD => 'Name', VALUE => $field);
         $CFs->LimitToLookupType($self->CustomFieldLookupType);
         $CFs->LimitToGlobalOrObjectId($self->Object->QueueObj->id);
         $field = $CFs->First->id if $CFs->First;
     }
 }
 return $self->SUPER::CustomFieldValues($field);

Has anyone else seen this and how can I fix it? As a result of this (I
presume), no ticket custom fields are being displayed.

Thanks,

Alison

Alison Downie, Computing Officer
School of Informatics, University of Edinburgh
Room B21, 5 Forrest Hill, EDINBURGH, EH1 2QL

Tel: 650 3095

I saw this too and this uninit warning is worrying me too, but I never
had chance to figure out impact of it, so I don’t recall any bug
report that may be caused by this code.On 2/5/07, Alison Downie alisond@inf.ed.ac.uk wrote:

I am trying to upgrade from 3.0.8 to 3.6.1 and am seeing this message in
the rt.log:

Use of uninitialized value in pattern match (m//) at
/opt/rt/lib/RT/Transaction_Overlay.pm line 1073

The bit that it seems to complain about is:

sub CustomFieldValues {
my $self = shift;
my $field = shift;

 if ( UNIVERSAL::can( $self->Object, 'QueueObj' ) ) {

=============> unless ( $field =~ /^\d+$/o ) { <===============

         my $CFs = RT::CustomFields->new( $self->CurrentUser );
          $CFs->Limit( FIELD => 'Name', VALUE => $field);
         $CFs->LimitToLookupType($self->CustomFieldLookupType);
         $CFs->LimitToGlobalOrObjectId($self->Object->QueueObj->id);
         $field = $CFs->First->id if $CFs->First;
     }
 }
 return $self->SUPER::CustomFieldValues($field);

Has anyone else seen this and how can I fix it? As a result of this (I
presume), no ticket custom fields are being displayed.

Thanks,

Alison


++++++++++++++++++++++++++++++++++++++++++++++
Alison Downie, Computing Officer
School of Informatics, University of Edinburgh
Room B21, 5 Forrest Hill, EDINBURGH, EH1 2QL

Tel: 650 3095
++++++++++++++++++++++++++++++++++++++++++++++


List info: The rt-devel Archives

Best regards, Ruslan.