I just got this back from Trillian support … I’'ve also requested a feature enhancement for this just to get them moving on this because there seems to be a lot of people in their forums that are having similar problems. If you need me to test anything on my end or need any debug info, let me know. I appreciate any help!!!
There are two ‘‘search’’ protocols for Jabber. One uses xdata –
basically, the server sends down a description of the search dialog,
and the results dialog, and the data to populate them – and the other,
older, method is called iq:search (and uses set fields).
iq:search is considered ‘‘deprecated’’ and newer clients are supposed to
use the xdata method instead of the generic hard-coded form. xdata is
better since it lets the server define available search fields and
methods, as well as the columns the search result returns, rather than
having hardcoded specific questions and results.
At any rate, Trillian supports the xdata method; the Jabber plugin was
written after the old method was deprecated. However, Psi, Exodus and
Spark have all been around long enough to have the older support. (In
fact, I don’'t believe Psi yet supports the newer protocol at all. I
know Exodus and Spark support both.)
A lot of the public Jabber servers don’'t support user searching at all,
which is problem enough. But it sounds like enough corporate servers
out there still use the old protocol that it would be worth my time to
add the older search method as well.
However, at present, Trillian only supports the newer xdata method
instead of the deprecated one. (Same is true of the old-style
‘‘register’’ and ‘‘browse’’ protocols; Trillian supports the xdata register
and disco feature discovery, instead of the older deprecated ones.)
Sorry for the inconvenience. :/[/i]