Contact blocking no longer works (#187)
Closed
Artur Hefczyc opened 5 years ago

I have chats on the list "from unknown". I click on the chat and then on a contact 'i' and select "Block contact". Then the status on the chat list does not change to blocked (there used to be red dot indicating that the contact us blocked). And when I open contact details again, the "Block contact" us unchecked.

Attached screenshots.

CleanShot 2020-01-22 at 12.42.10@2x.png CleanShot 2020-01-22 at 12.42.59@2x.png CleanShot 2020-01-22 at 12.43.38@2x.png

Andrzej Wójcik (Tigase) commented 5 years ago

What account and on which server are you using? Are you using any other client which could override privacy lists? Blocking actually overrides privacy lists so, if something would override it, blocking would be lost.

Artur Hefczyc commented 5 years ago

Actually, I did not think of checking on which account this happens. I will check next time. I am assigning this ticket to me until I collect more information.

Andrzej Wójcik (Tigase) commented 5 years ago

You can try to open XML console and check what is sent to the server while you click on Block contact and what is server response. It looks like there is Isode MLink 16.3v13 running at jabber.org but I do not have any idea about features available and provided by this server.

Artur Hefczyc commented 5 years ago

Actually, on all screenshots you can see that it was kobit@tigase.org account, so that was our, Tigase server involved. I have made some further investigation.

The same thing happened today.

I blocked contacts from the presence subscription request but on the chat list they appeared not blocked. I opened contact details and block checkbox was unchecked. Then I closed and reopened Beagle client and then on the chat list both contacts showed red dot, indicating they are blocked and also contact details showed they are blocked.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
Issue Votes (0)
Watchers (0)
Reference
tigase/_clients/beagle-im#187
Please wait...
Page is in error, reload to recover