MySQL Bugs: #37482: Custom fields not using defined APP

Bug #37482	Custom fields not using defined APP_CHARSET
Submitted:	18 Jun 2008 14:28	Modified:	1 May 2012 17:28
Reporter:	German Pizarro	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	Eventum	Severity:	S3 (Non-critical)
Version:	2.1.1	OS:	FreeBSD (6.1 i386)
Assigned to:	Bryan Alsdorf	CPU Architecture:	Any
Tags:	charset, custom, custom field, custom fields

Description:
This was already reported in the mailing list...
  http://lists.mysql.com/eventum-users/4650
...and it might be addressed in future version ("many changes commited improving handling of charset") but it's still an issue in 2.1.1

How to repeat:
-Change CHARSET to other than UTF-8, let's say ISO-8859-1 in config.php
-Create custom fields for project and use them in Report Issue Form
-Create issue entering spacial chars from the charset defined, ex. á é í ó ú ñ
-Display the custom fields in listing or export and check the spacial chars in custom fields. These characters are displayed/exported correctly in normal fields, but "incorrectly" (still using UTF-8 instead defined APP_CHARSET) in custom fields.

Suggested fix:
-Data is saved correctly in database, so it's only a display problem.
-Custom fields are run through an additional  method before display, Custom_Field::formatValue that could be causing this.
-Problem could be already fixed in SVN.

What is the characterset of your database tables? 

I have found in my testing that custom fields behave the same as other fields, and for best results you need to keep APP_CHARSET the same as the charset for your tables.

I will check the tables ASAP.

OK, the tables use utf8_general_ci
The APP_CHARSET was changed to UTF-8
A new issue was created with UTF-8 charset enabled, but the problem remains for CUSTOM fields.

Custom Fields  
Correo externo:  	Prueba con UTF-8 Ã‘andÃº 

Are you using standard Eventum 2.1.1?

Not supported anymore.