https://bugs.kde.org/show_bug.cgi?id=435409
--- Comment #16 from Angel Docampo <docampo.an...@gmail.com> --- >There is not caching so perhaps you change setting without restart ruqola and >ruqola doesn't react on it but if you relaunch it it will get permission etc >from server. That's exactly what I'm doing. Closing the session but not closing ruqola. When I close and re-open ruqola, permissions and visibility are shown properly More precisely, if I log in first with an unprivileged user and close the session, and re-open with an administrator user, permissions and visibility are shown properly: I can see and edit/delete posts If I do the contrary, close the session with a privileged user and re-open with an unprivileged user, I can see **the last chat where the administrator was connected**, and I'm able to see the "Edit" and "Delete" menu option, yet they throw an error. So the menu re-draws properly from non-privileged to privileged user but not vice-versa, and it happens the same with the conversation chat window: when I log off from an administrator account and log in with an unprivileged user, that unprivileged user sees the chat where the administrator was before the logout (although if he changes to another chat, he cannot see again the administrator chat conversation), but if with that unprivileged user I select a chat room where the administrator has no access and log off, and re-log on with the administrator account, it cannot see that chat. So, it seems re-drawing of the interface works with the admin account at logon time, but with the unprivileged user works at launch time. -- You are receiving this mail because: You are watching all bug changes.
