#945 members get kicked when on muc#roomconfig_membersonly change to enabled

Reporter pep.
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Type-Defect
  • Priority-Medium
  • Status-Fixed
  • Milestone-0.11
  1. pep. on

    What steps will reproduce the problem? 1. Create (join) a new room. You now are owner on it 2. Enable muc#roomconfig_membersonly What is the expected output? What do you see instead? I should stay on the room as owner. Instead I am kicked, "You have been kicked because you are not a member and the room is now members-only." This also happens to users I change the affiliation to member. What version of the product are you using? On what operating system? Prosody r8168+.45be94611593+-1 on Archlinux, poezio 20170619.4aa6e8e-1 to configure the muc. Please provide any additional information below. 00:30:51 IN <iq id="0c0a7c8e-490d-492b-b71f-260f994f21a0-B54" type="result" to="user@domain/res" from="bar@muc-server"><query xmlns="http://jabber.org/protocol/muc#owner"><x xmlns="jabber:x:data" type="form"><title>Configuration for bar@muc-server</title><instructions>Complete and submit this form to configure the room.</instructions><field type="hidden" var="FORM_TYPE"><value>http://jabber.org/protocol/muc#roomconfig</value></field><field type="text-single" label="Name" var="muc#roomconfig_roomname"><value>bar</value></field><field type="text-single" label="Description" var="muc#roomconfig_roomdesc"><value /></field><field type="boolean" label="Make Room Persistent?" var="muc#roomconfig_persistentroom" /><field type="boolean" label="Make Room Moderated?" var="muc#roomconfig_moderatedroom" /><field type="boolean" label="Make Room Publicly Searchable?" var="muc#roomconfig_publicroom"><value>1</value></field><field type="boolean" label="Make Room Members-Only?" var="muc#roomconfig_membersonly" /><field type="text-private" label="Password" var="muc#roomconfig_roomsecret"><value /></field><field type="boolean" label="Allow Occupants to Change Subject?" var="muc#roomconfig_changesubject" /><field type="list-single" label="Who May Discover Real JIDs?" var="muc#roomconfig_whois"><option label="Moderators Only"><value>moderators</value></option><value>moderators</value><option label="Anyone"><value>anyone</value></option></field><field type="text-single" label="Maximum Number of History Messages Returned by Room" var="muc#roomconfig_historylength"><value>20</value></field><field type="boolean" label="Notify absent users when their affiliation changes?" var="muc#roomconfig_affiliationnotify" /></x></query></iq> 00:30:56 OUT <iq id="0c0a7c8e-490d-492b-b71f-260f994f21a0-B55" type="set" to="bar@muc-server"><query xmlns="http://jabber.org/protocol/muc#owner"><x xmlns="jabber:x:data" type="submit"><instructions>Complete and submit this form to configure the room.</instructions><field var="FORM_TYPE"><value>http://jabber.org/protocol/muc#roomconfig</value></field><field var="muc#roomconfig_roomname"><value>bar</value></field><field var="muc#roomconfig_roomdesc"><value /></field><field var="muc#roomconfig_persistentroom"><value>0</value></field><field var="muc#roomconfig_moderatedroom"><value>0</value></field><field var="muc#roomconfig_publicroom"><value>1</value></field><field var="muc#roomconfig_membersonly"><value>1</value></field><field var="muc#roomconfig_roomsecret"><value /></field><field var="muc#roomconfig_changesubject"><value>0</value></field><field var="muc#roomconfig_whois"><value>moderators</value></field><field var="muc#roomconfig_historylength"><value>20</value></field><field var="muc#roomconfig_affiliationnotify"><value>0</value></field></x></query></iq> 00:30:56 IN <iq id="0c0a7c8e-490d-492b-b71f-260f994f21a0-B55" type="result" to="user@domain/res" from="bar@muc-server" /> 00:30:56 IN <message type="groupchat" to="user@domain/res" from="bar@muc-server" id="0c0a7c8e-490d-492b-b71f-260f994f21a0-B56"><x xmlns="http://jabber.org/protocol/muc#user"><status code="104" /></x></message>

  2. MattJ on

    Thanks for the report. Is this still an issue for you? I'm unable to reproduce it.

    Changes
    • tags Status-NeedInfo
  3. pep. on

    Yep! It works now, thanks.

  4. Zash on

    Changes
    • tags Status-Fixed Milestone-0.11

New comment

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