#1693 Wrong affiliation and role on destroy message from muc

Reporter damencho
Owner Nobody
Stars ★ (1)
  • Status-Accepted
  • Type-Defect
  • Priority-Medium
  1. damencho on

    What steps will reproduce the problem? 1. Destroy a room: echo "> hosts['conference.mydomain.com'].modules.muc.get_room_from_jid('damencho@conference.mydomain.com'):destroy()" | nc -w1 localhost 5582 2. Examine the messages received on a client connected to the room What is the expected output? Not sure :) Should have affiliation none maybe ... or missing that child node in the x element ... What do you see instead? <presence xmlns='jabber:client' xml:lang='en' to='focus@auth.mydomain.com/focus' from='damencho@conference.mydomain.com/focus' type='unavailable'> <x xmlns='http://jabber.org/protocol/muc#user'> <item affiliation='owner' jid='focus@auth.mydomain.com/focus' role='none'></item> <status code='110'/> <destroy></destroy> </x> </presence> What version of the product are you using? On what operating system? 0.11.10 Please provide any additional information below.

  2. Zash on

    Thanks. Agree that affiliation=none would make more sense, tho role=none (you're being kicked) does communicate what's going on, in a way, even if you don't understand <destroy>

    • tags Status-Accepted

New comment

Not published. Used for spam prevention and optional update notifications.