Always join as USER when joining group or public room
Allow nulls for Oracle
Changes after review
Removed populateBaseRoomData and reused the existing code by adding an
extra condition for when querying listable rooms with null participant.
Co-authored-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Added ability to set a conversation as listable for regular users and/or
guest users from the guest app.
This only implements the flag, endpoint and UI to manage it but not yet
making it appear in search results.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
By default API version 1 will be used. To use a specific API version
" (v1)", " (v2)" or " (v3)" can be appended to the step name.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This fixes a regression introduced in 4afa2d7946.
The active guests are only those who are currently in a call, and not
those who are currently in the conversation. Therefore other guests or
users were not prevented from joining a password request conversation if
a guest was in the conversation but not in the call.
Fortunately in practice this was not a problem, as the Web UI starts a
call immediately after joining the conversation, which made the guest
immediately active and thus prevented others from joining.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Until now it was possible to verify the room data when getting the full
room list with the "user is participant of the following rooms" step.
Now the same can be optionally done when using "user is participant of
room XXX" too.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Passing in the "body" request option as an array to send
a POST request has been deprecated. Please use the "form_params"
request option to send a application/x-www-form-urlencoded
request, or the "multipart" request option to send a
multipart/form-data request. (InvalidArgumentException)
Signed-off-by: Joas Schilling <coding@schilljs.com>
Self-joined users and guests can join the room for a file if the file is
shared by link. In order to check that, however, the share token should
have been previously stored in the session, as the room is linked to the
file id and users without direct access to a file can not find out if
the file is shared by link or not. Therefore self-joined users and
guests must get the room for the share (which stores the share token in
the session) before being able to join the room.
Besides that, in the case of self-joined users they must be logged in
too. Otherwise the session is regenerated on each new request, which
prevents getting the share token stored in a previous request.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The lobby constants were named from the point of view of the webinary
(open to all participants, open to moderators only), but from the point
of view of the lobby it is the opposite (no lobby, lobby for non
moderators).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
This forces the users and groups to be created again from scratch as
needed for each new scenario, thus preventing actions performed in a
previous scenario, like creating a new folder, from affecting the
following scenarios.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Vincent Petry
Joas Schilling
Daniel Calviño Sánchez