#424 Jabber Search

Reporter pm.debian
Owner Zash
Created
Updated
Stars ★ (1)  
Tags
  • Priority-Low
  • Type-Enhancement
  • Status-Fixed
  1. pm.debian on

    > What steps will reproduce the problem? 1. Set up Pidgin 2.10.9. 2. Configure the account on the Prosody system. 3. Go to accounts, choose the account from above and do search for users. > What is the expected output? What do you see instead? You’ll get the result “Service not available”. I want to get the user back. In the Prosody debug log, there are the lines below. Jun 27 12:38:18 c2s1a1b840 debug Received[c2s]: <iq id='purple6d846cb2' type='get' to='userisearchedfor@example.net'> Jun 27 12:38:18 stanzarouter debug Stanza of type iq from c2s has xmlns: jabber:iq:search Jun 27 12:38:18 stanzarouter debug Unhandled c2s stanza: iq; xmlns=jabber:iq:search Jun 27 12:39:09 c2s19bb6c0 debug Received[c2s]: <iq id='purplebe9dfbc8' type='get'> Jun 27 12:39:15 c2s1a1b840 debug Received[c2s]: <iq id='purple6d846cb3' type='get'> > What version of the product are you using? On what operating system? Prosody 0.9.4 on Debian Jessie/testing.

  2. Zash on

    Prosody does not ship with user search support. A community module for this is available: http://modules.prosody.im/mod_vjud.html

    Changes
    • title Jabber Search
    • tag Type-Enhancement
    • tag Priority-Low
  3. Zash on

    Closing this since this is/was a Pidgin problem with not doing service discovery to find out if user search is available, and since there's a community module available.

    Changes
    • tags Status-Fixed
    • owner Zash

New comment