3.0.1 issues

RT Users
1

Hi,

after updating from 3.0.0 to 3.0.1 we had two major problems:

  • any change done to a ticket with a screen that contains a field to change
    the subject
    leads to a deleted subject. After that a subject is displayed as “0”. It’s
    not possible
    to change the subject anymore. It’s alsways “0”
  • a mail containing german umlauts in the mail’s subject will generate a
    complete empty ticket
    without a requestor, subject and body.

Since this was a big handicap, I had to step back to 3.0.0 and delete the
mason_data and session_date subdirectories in /opt/rt3/var without any further
investigations.

my config:

Suse Linux 8.2
perl 5.8.0
apache 1.3.27
mod_perl 1.27
MySQL 3.23.55

Are these bugs already known? I did not find anything in the archives.

Arne

2

Arne Hinrichsen wrote:

Hi,

after updating from 3.0.0 to 3.0.1 we had two major problems:

  • any change done to a ticket with a screen that contains a field to change
    the subject
    leads to a deleted subject. After that a subject is displayed as “0”. It’s
    not possible
    to change the subject anymore. It’s alsways “0”
  • a mail containing german umlauts in the mail’s subject will generate a
    complete empty ticket
    without a requestor, subject and body.

I’m seeing problems with 3.0.2pre3 looking quite the same here, the
problem seems to be related to 8 bit characters, in my case ISO8859-1.

I can create tickets with 8 bit subject, and things seem fine - if I
edit the subject later, it gets changed to just “0”. The same thing
happens when changing info for users.

My enviroment is:
Redhat 8
Apache 2.0.40
mod_perl 1.99
perl 5.8.0
all dependencies satisfied
mySQL 4.0.12

3

I’m seeing problems with 3.0.2pre3 looking quite the same here, the
problem seems to be related to 8 bit characters, in my case ISO8859-1.

I can create tickets with 8 bit subject, and things seem fine - if I
edit the subject later, it gets changed to just “0”. The same thing
happens when changing info for users.
A quick but dirty fix is to remove the line
$value = $object->DecodeUTF8($value);
from sub UpdateRecordObj in lib/RT/Interface/Web.pm.

VAJK� P�ter Astron Informatikai Kft
Vahot u. 6.
tel: +36 1 481-2146 H-1115 Budapest
fax: +36 1 204-5395 Hungary

4

Vajk� P�ter wrote:

I’m seeing problems with 3.0.2pre3 looking quite the same here, the
problem seems to be related to 8 bit characters, in my case ISO8859-1.

I can create tickets with 8 bit subject, and things seem fine - if I
edit the subject later, it gets changed to just “0”. The same thing
happens when changing info for users.

A quick but dirty fix is to remove the line
$value = $object->DecodeUTF8($value);
from sub UpdateRecordObj in lib/RT/Interface/Web.pm.

Thanks, this seems to do the trick for now :slight_smile:

Roy-Magne Mo