Not logged in. · Lost password · Register
Forum: Community Pre-release Discussion RSS
MUC features in v0.12-RC2

Announcement

11-16-2005, 12:33 by halr9000
Subject: Psi Groupchat (new address)
Join us at the Psi Groupchat (MUC)! Room name: psi@conference.psi-im.org
userjoe #1
Member since 03/2008 · 6 posts
Group memberships: Members
Show profile · Link to this post
Subject: MUC features in v0.12-RC2
Sorry if this has already been answered but I am unable to use some MUC features such as editing the chat room Administrators, Banned and Members lists.  Is it possible to edit these MUC lists in 0.12-rc2 or it this a problem with the Jabber server that I am using?
Avatar
machekku #2
User title: Crazy guy from Poland
Member since 07/2004 · 805 posts · Location: Poland
Group memberships: Developers, Members
Show profile · Link to this post
Just to make sure: you have enough permissions to use these, don't you?
Maciek "Machekku" Niedzielski
Psi developer
[Image: http://machekku.uaznia.net/jabber/jobble/map/jmpixel1.png]
userjoe #3
Member since 03/2008 · 6 posts
Group memberships: Members
Show profile · Link to this post
Yes, I am creating a new chat room so I am the room owner.  I captured the XML from the XML console that I see when I click on the "Configure Room" option in the chat room. I am seeing some "<error code="400" >Invalid Namespace</error>".  What would cause the errors?  BTW the server that I am using is running mu-conference 0.6.0 bundled with JCR 0.2.4.  BTW I also tried editing the MUC affiliations when logged into jabber.org and saw the same issue.  The XML is below ( I changed the jabber server name for this post):


<iq type="get" to="psitesting@conference.jabberserv.org" id="acb7a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="outcast" />
</query>
</iq>


<iq type="get" to="psitesting@conference.jabberserv.org" id="acb8a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="member" />
</query>
</iq>


<iq type="get" to="psitesting@conference.jabberserv.org" id="acb9a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="admin" />
</query>
</iq>


<iq type="get" to="psitesting@conference.jabberserv.org" id="acbaa" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="owner" />
</query>
</iq>


<iq from="psitesting@conference.jabberserv.org" type="error" to="me@jabberserv.org/Psi" id="acb7a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="outcast" />
</query>
</iq>


<iq from="psitesting@conference.jabberserv.org" type="error" to="me@jabberserv.org/Psi" id="acb8a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="member" />
</query>
</iq>


<iq from="psitesting@conference.jabberserv.org" type="error" to="me@jabberserv.org/Psi" id="acb9a" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="admin" >
<error code="400" >Invalid Namespace</error>
</item>
</query>
</iq>


<iq from="psitesting@conference.jabberserv.org" type="error" to="me@jabberserv.org/Psi" id="acbaa" >
<query xmlns="http://jabber.org/protocol/muc#admin">
<item affiliation="owner" >
<error code="400" >Invalid Namespace</error>
</item>
</query>
</iq>
userjoe #4
Member since 03/2008 · 6 posts
Group memberships: Members
Show profile · Link to this post
FYI I received the following response after posting this same question to the mu-conference-talk list on gna.org.  Thanks to Gregoire for his reply.  I plan to update my mu-conference version and see if I can edit the MUC room affiliations lists in Psi after that.


I think the problem come from mu-conf 0.6, it was still using the owner
namespace for requesting the admin and owner lists. The last few revisions of
the XEP 0045 changed this to use the admin namespace for all the lists. This
would explain the errors when getting the admin and owner lists. But for the
errors for the two other lists I have no idea.

Regards,
Greg
userjoe #5
Member since 03/2008 · 6 posts
Group memberships: Members
Show profile · Link to this post
Just to follow up, updating to mu-conference 0.7 did fix these issues with MUC room affiliations.  Thanks Greg.
Close Smaller – Larger + Reply to this post:
Smilies: :mellow: :huh: ^_^ :o ;) :P :D :lol: B) :rolleyes: -_- <_< :) :wub: :angry: :( :unsure: :wacko: :blink: :ph34r:
Special characters:
Go to forum
Unclassified NewsBoard devel of 20051113 © 2003-5 by Yves Goergen
Current time: 07-24-2008, 11:56:06 (UTC -04:00)