6.0.0-beta1
7/16/25

[#6457] utf-8 error on attendee's addressbook search
Summary utf-8 error on attendee's addressbook search
Queue Kronolith
Queue Version 2.2-RC2
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester szimszon (at) oregpreshaz (dot) eu
Created 03/17/2008 (6330 days ago)
Due
Updated 11/09/2008 (6093 days ago)
Assigned 04/25/2008 (6291 days ago)
Resolved 11/09/2008 (6093 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/09/2008 03:38:59 AM Chuck Hagenbuch State ⇒ No Feedback
 
04/25/2008 07:11:57 AM szimszon (at) oregpreshaz (dot) eu Comment #24 Reply to this comment
Well, that makes it exactly the same as the IMP code, so, we need
more information from you on why it doesn't work on your system.
Who can I help?



Who could I make the problem more verbose? Could you send me a code 
with more logging? What shall I do?
04/25/2008 07:00:21 AM Chuck Hagenbuch Comment #23
Taken from Chuck Hagenbuch
State ⇒ Stalled
Reply to this comment
Well, that makes it exactly the same as the IMP code, so, we need more 
information from you on why it doesn't work on your system.
04/25/2008 06:54:36 AM szimszon (at) oregpreshaz (dot) eu Comment #22 Reply to this comment
It doesn't work for me :(



I downloaded the 
"http://cvs.horde.org/co.php?r=1.1.2.2&p=1&f=kronolith%2Flib%2FJSON.php" and 
replaced the JSON.php in /kronolith/lib but the result is the same as 
previous.



I deleted my browser's cache restarted the apache deleted the horde 
cache files... :(
04/25/2008 03:52:37 AM Chuck Hagenbuch Comment #21
State ⇒ Resolved
Reply to this comment
04/25/2008 03:39:19 AM Chuck Hagenbuch Comment #20
State ⇒ Assigned
Assigned to Chuck Hagenbuch
Reply to this comment
The other way around.
04/24/2008 11:18:50 AM szimszon (at) oregpreshaz (dot) eu Comment #19 Reply to this comment
It's a symptom of the same PHP problem, not the same Horde problem.
Address search uses JSON; you probably need a newer PHP json module.
But why is it working elsewhere on my system? Look at new_mail_ok.png



Or only kronolith use json for address expansion/search and IMP not?
04/23/2008 10:01:17 PM Chuck Hagenbuch Comment #18
State ⇒ Duplicate
Reply to this comment
It's a symptom of the same PHP problem, not the same Horde problem. 
Address search uses JSON; you probably need a newer PHP json module.
04/08/2008 04:44:02 PM szimszon (at) oregpreshaz (dot) eu Comment #17 Reply to this comment
Eh, bug 5955. :)
I have no problem with Subject's in DIMP :-o Everything is fine.
04/07/2008 10:16:58 AM Jan Schneider Comment #16 Reply to this comment
This is the bug #6457... :)
Eh, bug 5955. :)
04/07/2008 07:02:00 AM szimszon (at) oregpreshaz (dot) eu Comment #15 Reply to this comment
See also bug 6457 which might be
another symptom of the same root problem.
This is the bug #6457... :)
04/07/2008 06:58:32 AM szimszon (at) oregpreshaz (dot) eu Comment #14 Reply to this comment
Which PHP version do you use? See also bug 6457 which might be
another symptom of the same root problem.
Package: php5

Status: install ok installed

Priority: optional

Section: web

Installed-Size: 20

Maintainer: Debian PHP Maintainers <pkg-php-maint@lists.alioth.debian.org>

Architecture: all

Version: 5.2.0-8+etch10


04/04/2008 12:30:33 PM Jan Schneider Version ⇒ 2.2-RC2
Queue ⇒ Kronolith
 
04/04/2008 12:29:53 PM Jan Schneider Comment #13 Reply to this comment
Which PHP version do you use? See also bug 6457 which might be another 
symptom of the same root problem.
03/20/2008 02:49:26 PM szimszon (at) oregpreshaz (dot) eu Comment #12 Reply to this comment
Do you have the json PHP extension installed by chance? We seem to
use it in IMP if it's available, but not in Kronolith. This could
make the difference.
I use this extension:



dpkg -s php5-json

Package: php5-json

Status: install ok installed

Installed-Size: 60

Maintainer: Pierre Habouzit <madcoder@debian.org>

Architecture: i386

Source: php-json-ext

Version: 1.2.1-3.2



extension=json.so


03/20/2008 12:12:40 PM Jan Schneider Comment #11 Reply to this comment
Do you have the json PHP extension installed by chance? We seem to use 
it in IMP if it's available, but not in Kronolith. This could make the 
difference.
03/20/2008 12:11:21 PM Jan Schneider Comment #10 Reply to this comment
And in IMP's compose.php:

$js_code[] = 'var identities = ' .
IMP_Serialize_JSON::encode(String::convertCharset($js_ident,
NLS::getCharset()), 'utf-8');
Nice catch. It was actually the line in IMP that was wrong.
03/20/2008 10:06:37 AM szimszon (at) oregpreshaz (dot) eu Comment #9 Reply to this comment
My SQL settings are:



$conf['sql']['persistent'] = true;

$conf['sql']['username'] = 'xxxxxxx';

$conf['sql']['password'] = '**********';

$conf['sql']['hostspec'] = 'localhost';

$conf['sql']['port'] = 0;

$conf['sql']['protocol'] = 'tcp';

$conf['sql']['database'] = 'hordewebmail2';

$conf['sql']['charset'] = 'utf-8';

$conf['sql']['phptype'] = 'pgsql';


03/20/2008 10:03:03 AM szimszon (at) oregpreshaz (dot) eu Comment #8 Reply to this comment
Sorry I have not much time these days... :(



I found some interesting line but it seems to have no effect to my problem.



In kronolith's imle.php I found the line:

   echo 
KRONOLITH_Serialize_JSON::encode(String::convertCharset($result, 
NLS::getCharset(), 'utf-8'));



(String::convertCharset($result, NLS::getCharset(), 'utf-8' -->)<-- );



And in IMP's compose.php:



$js_code[] = 'var identities = ' . 
IMP_Serialize_JSON::encode(String::convertCharset($js_ident, 
NLS::getCharset()), 'utf-8');



(String::convertCharset($js_ident, NLS::getCharset()  -->)<--  , 'utf-8');



In kronolith's code, the 'utf-8' is the argument of 
String::convertCharset but not in IMP's code...



Anyway change it in kronolith doesn't do the trick :(






03/17/2008 05:18:54 PM Jan Schneider Comment #7
State ⇒ Feedback
Reply to this comment
If you know your way around charsets, you should start in 
kronolith/imple.php where the conversion happens from the turba api to 
json (javascript) code.
03/17/2008 03:13:52 PM szimszon (at) oregpreshaz (dot) eu Comment #6 Reply to this comment
Works fine here
I don't know if it matters, I have pgsql database backend.



How can I trace the problem back?
03/17/2008 02:47:39 PM Jan Schneider Comment #5 Reply to this comment
Works fine here
03/17/2008 02:18:11 PM szimszon (at) oregpreshaz (dot) eu Comment #4
New Attachment: attendee2_wrong.png Download
Reply to this comment
Attendee wrong: attendee2_wrong.png
03/17/2008 02:17:24 PM szimszon (at) oregpreshaz (dot) eu Comment #3
New Attachment: attendee_wrong.png Download
Reply to this comment
Attendee expand wrong: attendee_wrong.png
03/17/2008 02:16:48 PM szimszon (at) oregpreshaz (dot) eu Comment #2
New Attachment: new_mail_ok.png Download
Reply to this comment
If I make a new e-mail it's OK: new_mail_ok.png
03/17/2008 02:15:43 PM szimszon (at) oregpreshaz (dot) eu Comment #1
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: contact.png Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Type ⇒ Bug
Summary ⇒ utf-8 error on attendee's addressbook search
Reply to this comment
I wonder if somebody could help me...



I have a contact named "Árvízt&#369;r&#337; Tükörfúrógép".



Everywhere looks ok but if I make a new event and I assign attendees to it.

The addressbook autoexpand looks bad.



My contact info: contact.png

If I make a new e-mail it's OK: new_mail_ok.png

Attendee expand wrong: attendee_wrong.png

Attendee wrong: attendee2_wrong.png

Saved Queries