Hi,
> Anyway, if you use OTRS 1.2.2, follow the following:
> o Update Kernel/System/CustomerUser/LDAP.pm to 1.16
Ok, here is my problem number on:
in your package otrs-1.2.4-01 the version of LDAP.pm is 1.15
In your packages otrs-1.3.x the version of LDAP.pm is 1.21
Is the exact version important
Hi Matthias,
On Tue, Aug 31, 2004 at 09:57:28AM +0200, Matthias Eichler wrote:
> > a) Let OTRS work in UTF-8 charset (then you also need a utf-8 able
> > database, e. g. MySQL 4.1 or higher)
> > b) Convert UTF-8 to e. g. iso-8859-1 which config settings in CustomerUser
> > config object:
>
Hi Martin,
Am Dienstag, den 31.08.2004, 06:44 +0200 schrieb Martin Edenhofer:
> a) Let OTRS work in UTF-8 charset (then you also need a utf-8 able
> database, e. g. MySQL 4.1 or higher)
> b) Convert UTF-8 to e. g. iso-8859-1 which config settings in CustomerUser
> config object:
Hm...is so
Hi Matthias,
On Fri, Aug 27, 2004 at 12:57:33PM +0200, Matthias Eichler wrote:
> I've just entered all the customerdata from our groupware
> database into the LDAP directory.
> The entries went into the LDAP as UTF8 converted strings.
>
> Now the CustomerUser function works for searching etc.,
>
Dear List,
I've just entered all the customerdata from our groupware
database into the LDAP directory.
The entries went into the LDAP as UTF8 converted strings.
Now the CustomerUser function works for searching etc.,
BUT all german Umlaute are not displayed correctly by
OTRS.
All other applicati
