Joined Groupchats do not appear in UI
haroldkyle opened this issue · 6 comments
I think that when I join a Groupchat, the chat room is supposed to appear under "Groupchats" in the UI. Nothing appears there when I'm in a room. When I've joined several rooms, and a notification for a new message happens, there's no way to tell which room prompted the notification. No list of joined groupchats appears in the interface at all, that I can find at the moment.
Could you try using the bookmarks plugin for Openfire to create a few bookmarks and confirm if they show.
Funny you should bring up Bookmarks. These are also failing. From the console:
<error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error>
I hadn't mentioned the bookmark error because my plugins were out of date and it seemed like a server issue. I have now updated all plugins (Bookmarks to 1.0.3) and also Openfire itself to 4.5.1. I still cannot see open groupchats nor save a bookmark. Also, a bookmark I created on the server directly is not properly fetched at launch. The error is the same 503 as above.
There are 2 types of bookmarks. Bookmarks created by the client that are stored server-side as PEP data and bookmarks created on the server by the admin. Looks like none are working.
The only time I have seen this happen is when two different clients like Conversations and Converse try to use the same bookmarks and they stop working. All I can suggest is delete all PEP bookmarks, do a factory reset in Pade and start again.
I don't have a section for Users > User Options. Here is what my installation looks like:
Separately, I see bookmarks (empty) under Server:
I made sure to perform a factory reset Pade prior to posting this bug. I factory reset again after updating plugins earlier today. Still, no change. Is there anything else I could do to help track this bug down?
OK I found the "Personal Eventing" under my individual user. I deleted all leaf nodes, including one for bookmarks. I performed another factory reset. Still no luck.
I finally found the issue. It is fixed in 1.6.3
Pade creates a dummy self user for logged in user. This was happening too early and creating the issue.