Is anyone else using RT 3.8.0 with $LdapExternalInfo set to enabled?
It seems that the behavior on looking up information from the LDAP
information has changed between 3.6.6 and 3.8.0 (which is to be
expected) but for the worse. In previous releases it would do a lookup
on login and update your information. This is good. However now it
seems that is doing a lookup against everyone ever messaged on a
ticket when I hit ‘comment’ or ‘reply’ via the interface. The browser
meanwhile sits and waits patiently but the rt login (set to debug for
this purpose) fills up with lookup requests on anyone ever commenting,
cc’d (even one-time ccs) or reply to the ticket. On a new ticket this
is no big deal as usually its only two or three people affected but
project tickets where 14-15 people are referenced, this becomes a huge
bother.
Anyone else seeing this and have figured out a way around this?
Yvo
Retrying here as this is really a performance killer and no idea on
how to solve…---------- Forwarded message ----------
From: Yvo van Doorn yvo.vandoorn@gmail.com
Date: Thu, Jul 17, 2008 at 8:35 AM
Subject: RT 3.8.0 and $LdapExternalInfo
To: rt-users@lists.bestpractical.com
Is anyone else using RT 3.8.0 with $LdapExternalInfo set to enabled?
It seems that the behavior on looking up information from the LDAP
information has changed between 3.6.6 and 3.8.0 (which is to be
expected) but for the worse. In previous releases it would do a lookup
on login and update your information. This is good. However now it
seems that is doing a lookup against everyone ever messaged on a
ticket when I hit ‘comment’ or ‘reply’ via the interface. The browser
meanwhile sits and waits patiently but the rt login (set to debug for
this purpose) fills up with lookup requests on anyone ever commenting,
cc’d (even one-time ccs) or reply to the ticket. On a new ticket this
is no big deal as usually its only two or three people affected but
project tickets where 14-15 people are referenced, this becomes a huge
bother.
Anyone else seeing this and have figured out a way around this?
Yvo