* update(chat): add option to disable private chat
- Adds `public.chat.private` to settings.yml, defaults to true
- Adds `privateChat` to disabledFeatures
* backend validation for disabledFeatures=privateChat
* refactor(settings): remove chat.private from settings.yml
Will be kept only in disabledFeatures
---------
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
I/O device IDs are logged in some specific logCodes, but they aren't too
useful on their own without the rest of the MediaDeviceInfo object. We
need that extra data (label, group) to be able to better investigate
incorrect device issues and NotFoundError occurrences.
Register full I/O device info whenever the client fetches them and add
those, unfiltered, to the following logCodes:
- audiomanager_error_getting_device
- audiomanager_error_device_not_found
- audiomanager_error_unknown
- audio_joined
- audio_ended
- audio_failure
- audiomanager_input_live_device_change_failure
- audiomanager_output_device_change_failure
* Enable LearningDashboard cookie support across different subdomains.
After a meeting ends, the client sets a cookie `ld-${meetingId}` with a token used to retrieve meeting data in JSON format. The Learning Dashboard needs access to this cookie to obtain the token.
The issue occurs in a Cluster setup where the Dashboard is hosted on a different subdomain, preventing it from accessing the cookie.
To resolve this, the client will set the cookie using the root domain (excluding the subdomain). This allows the cookie to be accessible from any subdomain.
* lint fixes
* Update bigbluebutton-html5/imports/ui/components/meeting-ended/service.ts
Co-authored-by: Anton Georgiev <antobinary@users.noreply.github.com>
---------
Co-authored-by: Anton Georgiev <antobinary@users.noreply.github.com>
* feat(recording): adds custom "bbb_record_permission" userdata
Adds two new userdata parameters:
- bbb_record_permission: if true, bypass the moderator/viewer role permission and allows the user to start/stop the recording
- bbb_record_permission_tooltip: a string to show in the tooltip when the user don't have permission, useful to explain why the user can't start recording
This enables integrations to have custom rules for specific users to have or not permission to record a meeting
* chore(docs): adds new recording userdata to docs
* refactor: clean unused code
* Update docs/docs/administration/customize.md
Co-authored-by: Anton Georgiev <antobinary@users.noreply.github.com>
---------
Co-authored-by: Anton Georgiev <antobinary@users.noreply.github.com>
* feat(layout): add `hideTopRow` to nav bar context
Adds the `hideTopRow` property to the navbar in the layout context, allowing
the top row of the navigation bar to be hidden. Only the row with the
talking indicators and timer indicator will remain visible when this
option is used.
* feat(layout): add userdata `bbb_hide_controls`
Introduces the userdata join parameter `bbb_hide_controls`, which hides
the action bar and the top row of the navigation bar (including the close
sidebar button, room title, connectivity indicator, and leave meeting button)
while keeping the row with the talking indicator and timer indicator visible.
* fix(layout): has actions bar boolean expression
* feat(layout): add `hideNotificationToasts` to notifications bar
context
Adds the `hideNotificationToasts` property to the notifications bar
in the layout context, allowing the notification toasts to be
hidden when the property is set to `true`.
* feat(layout): add userdata `bbb_hide_notifications`
Introduces join userdata parameter `bbb_hide_notifications` that
prevents the rendering of all notification toasts in the client.
* feat(plugins): set away and set speaker level ui commands
Adds set away and set speaker level to plugins ui commands.
* fix(plugins): clear event listener in ui commands
Properly remove event listener in user status and conference ui
commands.
* chore: sync SDK version
Updates SDK to v0.0.62
* feat(plugins): adjust the set away command
Ensures the current away status is used to mute the microphone correctly
when the away status is set to true. Additionaly, adds a dependency array
for the pertinent values to be updated in the event listener callback.
* chore: update SDK version
Updates SDK to v0.0.65
* chore: update SDK version to 0.0.66
Updates SDK to v0.0.66
* fix(plugins): layout content pile hook improvements
The isOpen property of the content was not being updated when the minimize button was pressed, so plugins couldn't know if it was open or not.
Also, plugins were not receiving the initial state when subscribing to the hook, they only received subsequent changes.
+ fix duplicated external video event and user list event with wrong names.
* fix: eslint errors
* fix(layout): remove previous content from pile
Always remove previous content from pile when calling SET_PILE_CONTENT_FOR_PRESENTATION_AREA with open = false
* Update en.json
* Update settings.yml
* Create transcriptionLocale.ts
* Update component.tsx
* Update component.tsx
* Revert IN -> ID
Because it will be fixed in the main repository
* let -> const message
British -> GB
* Refactor audio captions messages and locales to fix issues reported by typescript code validation
---------
Co-authored-by: Ramón Souza <contato@ramonsouza.com>
This commit removes some actions and interactions that a bot user should
not be part:
- No actions available when clicking over bot user in the user-list
- Remove bot from exported user-list
- Remove bot from available users to be assigned to breakouts
- Sort reactions by least recent and then by reaction count.
- Wrong condition for checking if a user is moderator was preventing moderators rom reacting to messages if locking public chat was activated.
- Wrong condition for checking if a user is moderator was preventing moderators from editing messages if locking public chat was activated.
- Display message time for all messages.
Parent room's moderators are able to kick users from breakout rooms.
Included a new userdata `userdata-bbb_parent_room_moderator` so akka-apps can
signal the HTML5 client that the user had a moderator role when the breakout room
was created. This user will have an extra permission inside the breakout room where
he/she will be able to kick other users out.
