Page MenuHomePhabricator
Create Task
Maniphest T10897

Recovering a lost room in Conpherence
Closed, ResolvedPublic
Actions

Description

Steps to reproduce :

  1. Create new room, with a single participant
  2. Speak inside this room
  3. Remove yourself from the room
  4. Accept the warning message

As a result, you are locked outside of this dead room. I understand that this may be the desired flow. However, is there a possible admin work-around to recover the messages inside the room? As an admin (or a system admin), can I force adding myself back into the room?

Versions

Related Objects

Event Timeline

frederic.marbach created this task.Apr 29 2016, 6:55 AM
eadler added a subscriber: eadler.Apr 29 2016, 7:16 AM

you can likely manually modify the conference_participant table in ${NAMESPACE}_conpherence. The structure is straightforward.
This is likely not a good idea to do on a regular basis.

epriestley closed this task as Resolved.Apr 29 2016, 1:39 PM
epriestley claimed this task.
epriestley added a subscriber: epriestley.

If you know the ID/monogram of the room (should be in the subject of any email you received, looks like Z123), I think you can also bin/policy unlock Zxxx it, which should make it public. Then you should be able to rejoin it.

Overall, this behavior is expected and the prompt is explicit about the consequences, so I don't think this is a bug:

never.png (199×616 px, 15 KB)

That "Okay" button should really say "Abandon Room Forever" or similar for consistency, but there are some not-so-great technical reasons it doesn't. I'd expect this to get cleaned up in the next iteration of Conpherence (T10364).

There's also nothing else we could really do here except not let you leave rooms like this.

We could possibly write some bin/conpherence rejoin sort of script, but I'd like to have a better understanding of why users are confirming this operation despite the prompt explicitly warning them of the consequences first -- maybe we can do a better job of addressing some precursor situation.

Phabricator · Built by Phacility