[rt-users] Problem: Non-ASCII characters as Custom field values

[Volker Goetz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm trying to add values with non ASCII characters in it (German Umlaut, 
e.g. ä = ä) to custom fields. The values are stored correctly in the 
database; they are also displayed correctly in the web frontend in either 
the configuration section and also when adding/editing a particular 
ticket.

The value of the custom field, however, can only be changed to another 
value when and only when the current value does ONLY contain plain ASCII 
characters (i.e. a-z 0-9). It then can be changed to any value available, 
including those with german umlauts.

Once a value with umlauts is selected it is impossible to change it 
correctly. Custom fields with "select one value" behaviour are broken 
sucht that the new value does not replace the old values but it is added, 
rusulting that the "select one value" field actually has two values.

Cause of the fault seems to be that RT cannot find the old value (with 
umlauts) to delete, before it adds the new value.

Environment:
RT 2.0.7_01
RedHat 9
Apache 2.0.48 (own build)
PostgreSQL 7.4 (own build)
Perl 5.8.0 + required modules

The umlaut problem within ticket bodies, as discussed a few days ago, is 
solved with the patch that has been sent to the list.


- -- 

Volker Götz

- ---------------------------------------------------------------
section(one               Mail goetz at sectionone.de
Dipl.-Inform. Univ.       Web  http://www.sectionone.de/
Volker Götz               Tel. 0 30 / 40 00 67 9-0
Rosa-Luxemburg-Straße 15  Fax  0 30 / 40 00 67 9-15
10178 Berlin              PGP  4FEB1C34 @ wwwkeys.de.pgp.net
- ---------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/xiqHWM9gHU/rHDQRAhh6AJ9biMIver1XAszUwGeGTmrXkYmY3gCeOmV0
3X7NCfBDCVt5YV8fxLmLFcE=
=4zU+
-----END PGP SIGNATURE-----