[ejabberd] ejabberd 12.12.beta's bugs

Badlop badlop at gmail.com
Fri Dec 9 15:10:36 MSK 2016


Ok, finally I can reproduce the problem, it's a bug in the
set_room_affiliation command!

It's fixed for the next release, you can see it in:
https://github.com/processone/ejabberd/commit/1a4f63f058cbbb81493ce79242b1fb43bbed4b4e


--
Badlop
ProcessOne


On 7 December 2016 at 09:58, jacob jabber <ejabberd.jacob at gmail.com> wrote:
> thanks alot  badlop.
> I have changed affiliation with set_affiliation command in server,
> subscriber's removed.
>  when I did with iq  there is no problems
> <iq   from='user2 at example.com'
>     id='member1'
>     to='g8 at conference.example.com'
>     type='set'>
>   <query xmlns='http://jabber.org/protocol/muc#admin'>
>     <item affiliation='member'
>           jid='user3 at example.com'
>           nick='thirdwitch'/>
>   </query>
> </iq>
>
>
>
>
>
>
> On Tue, Dec 6, 2016 at 12:30 PM, <ejabberd-request at jabber.ru> wrote:
>>
>> Send ejabberd mailing list submissions to
>>         ejabberd at jabber.ru
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://lists.jabber.ru/mailman/listinfo/ejabberd
>> or, via email, send a message with subject or body 'help' to
>>         ejabberd-request at jabber.ru
>>
>> You can reach the person managing the list at
>>         ejabberd-owner at jabber.ru
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ejabberd digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: ejabberd 12.12.beta's bugs (Badlop)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 5 Dec 2016 17:41:56 +0100
>> From: Badlop <badlop at gmail.com>
>> To: ejabberd at jabber.ru
>> Subject: Re: [ejabberd] ejabberd 12.12.beta's bugs
>> Message-ID:
>>
>> <CAA6KaLy+fmUXQ_VzvZQ5CyTpGLZY6+qCe0X4MciLggGXV7uLvA at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi,
>>
>> I installed ejabberd 16.12-beta1, configured mod_muc to use sql,
>> created three accounts and tried to reproduce your problem. When user1
>> removes membership of somebody, the subscribers list is stored
>> correctly.
>>
>> When a user subscribes, do you see in logs a "UPDATE muc_room" with
>> correct subscribers, or not?
>>
>> Later, when you see in logs a "UPDATE muc_room" with no subscribers,
>> are the subscriptions working correctly? Do subscribers get messages
>> correctly? Does the admin get the correct list of subscribers?
>> <iq to='sala1 at conference.localhost'
>>     type='get'
>>     id='E6E10350-76CF-40C6-B91B-1EA08C332FC7'>
>>   <subscriptions xmlns='urn:xmpp:mucsub:0' />
>> </iq>
>> <iq to='user1 at localhost/tka1'
>>   from='sala1 at conference.localhost'
>>   type='result'
>>   id='E6E10350-76CF-40C6-B91B-1EA08C332FC7'>
>>   <subscriptions xmlns='urn:xmpp:mucsub:0'>
>>     <subscription jid='user3 at localhost'/>
>>   </subscriptions>
>> </iq>
>>
>>
>> ---
>> Badlop
>> ProcessOne
>>
>>
>>
>> On 5 December 2016 at 07:49, jacob jabber <ejabberd.jacob at gmail.com>
>> wrote:
>> > Hi . I using ejabberd 12.12.beta.
>> > In muc/sub when i have g5's group
>> > g5
>> > owner: user1
>> > member: user2,user3
>> > subscribers: user4, user5
>> >  when change affiliation user2 or add new members, removed subscribers.
>> >
>> >
>> > ejabberd update muc_room and removed subscribers,
>> >
>> > 2016-12-05 09:56:22.808 [debug]
>> > <0.385.0>@ejabberd_sql:sql_query_internal:570 SQL: "UPDATE muc_room SET
>> > opts='[{title,<<>>},\n {vcard,<<>>},\n
>> > {voice_request_min_interval,1800},\n
>> > {allow_change_subj,true},\n {allow_query_users,true},\n
>> > {allow_private_messages,true},\n
>> > {allow_private_messages_from_visitors,anyone},\n
>> > {allow_visitor_status,true},\n {allow_visitor_nickchange,true},\n
>> > {allow_voice_requests,true},\n {public,false},\n {public_list,false},\n
>> > {persistent,true},\n {mam,false},\n {moderated,true},\n
>> > {members_by_default,true},\n {members_only,false},\n
>> > {allow_user_invites,false},\n {password_protected,false},\n
>> > {password,<<>>},\n {anonymous,true},\n {captcha_protected,false},\n
>> > {description,<<>>},\n {logging,true},\n {max_users,200},\n
>> >
>> > {affiliations,[{{<<\"user3\">>,<<\"example.com\">>,<<>>},{member,<<>>}},\n
>> > {{<<\"user2\">>,<<\"example.com\">>,<<>>},{member,<<>>}},\n
>> > {{<<\"user1\">>,<<\"example.com\">>,<<>>},{owner,<<>>}}]},\n
>> > {subject,<<>>},\n {subject_author,<<>>}]' WHERE name='g5' AND
>> > host='conference.example.com'"
>> > 2016-12-05 09:56:22.808 [debug]
>> > <0.385.0>@ejabberd_sql:sql_query_internal:570 SQL: "commit;"
>> >
>> > Is this a bug?
>> > when subscribers have to  removed?
>> > thanks
>> >
>> >
>> >
>> > _______________________________________________
>> > ejabberd mailing list
>> > ejabberd at jabber.ru
>> > http://lists.jabber.ru/mailman/listinfo/ejabberd
>> >
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> ejabberd mailing list
>> ejabberd at jabber.ru
>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>>
>> ------------------------------
>>
>> End of ejabberd Digest, Vol 161, Issue 3
>> ****************************************
>
>
>
>
> --
>
> Best Regards
>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>


More information about the ejabberd mailing list