room locked upon creation (#13)

room locked upon creation (#13)

Activities

	tom quas opened 1 decade ago despite configuring the server with `muc/muc-lock-new-room[B]=false` tigase responds with the message below upon creation of a MUC room: `<body xmpp:version="1.0" ack="2440806" secure="true" xmlns:stream="http://etherx .jabber.org/streams" from="example.com" xmlns="http://jabber.org/protocol/httpbin d" xmlns:xmpp="urn:xmpp:xbosh"><message from="9ac@conference.example.com" xmlns=" jabber:client" to="x@example.com/77953" type="groupchat"><body>Room is locked. Please configure.</body></message></body >` this doesn't sound right... plus it locks out my clients if they don't implement proper unlock handling. environment: tigase-server and -muc jars from trunk, revision date 2011-03-11
	tom quas commented 1 decade ago sorry, forgot the initial presence request: <body secure="true" from="example.com" xmlns="http://jabber.org/protocol/httpbind " xmlns:xmpp="urn:xmpp:xbosh" xmpp:version="1.0" xmlns:stream="http://etherx.jab ber.org/streams" ack="7116792"><presence xmlns="jabber:client" from="9ac@confere nce.example.com/anon-69849860" to="x@example.co m/mobile_40254"><x xmlns="http://example.com/profile"><geocell>9ac7be3r</geocell> <nickname>anon-69849860</nickname></x><x xmlns="http://jabber.org/protocol/muc#u ser"><status code="110"/><status code="201"/><item affiliation="owner" role="mod erator" jid="xA@example.com/40254" nick= "anon-69849860"/></x></presence></body>
	tom quas commented 1 decade ago sorry, forgot the initial presence request: <body secure="true" from="example.com" xmlns="http://jabber.org/protocol/httpbind " xmlns:xmpp="urn:xmpp:xbosh" xmpp:version="1.0" xmlns:stream="http://etherx.jab ber.org/streams" ack="7116792"><presence xmlns="jabber:client" from="9ac@confere nce.example.com/anon-69849860" to="x@example.co m/mobile_40254"><x xmlns="http://example.com/profile"><geocell>9ac7be3r</geocell> <nickname>anon-69849860</nickname></x><x xmlns="http://jabber.org/protocol/muc#u ser"><status code="110"/><status code="201"/><item affiliation="owner" role="mod erator" jid="xA@example.com/40254" nick= "anon-69849860"/></x></presence></body>
	Bartosz Małkowski commented 1 decade ago I can't reproduce your problem. I used MUC component from trunk (revision 207). Configuration: `--comp-class-1 = tigase.muc.MUCComponent --comp-name-1 = muc muc/muc-lock-new-room[B]=false`
	tom quas commented 1 decade ago You're right, everything works great. There was a typo on --comp-name-1=muc which caused the configurator to ignore the lock setting. Sorry for the inconvenience.

Type	Bug
Priority	Critical
Assignee	Bartosz Małkowski
RedmineID	100

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-muc#13

Please wait...

Page is in error, reload to recover