-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
5.1
-
MOODLE_501_STABLE
-
Requirements
- A BigBlueButton server is setup:
- To set up the BBB server, you can register at https://registration-portal.blindsidenetworks.com/ to obtain credentials.
Setup
- Login as admin.
- Go to Site administration > Plugins > Manage activities and enable the BigBlueButton plugin.
- Go to BBB settings and configure the BigBlueButton server URL and BigBlueButton shared secret.
- Go to Site administration > Plugins > BigBlueButton > Experimental Settings and enable Register live sessions (bigbluebuttonbn_meetingevents_enabled)
- Go to Site administration > Development > and enable DEBUG_DEVELOPER.
- Install the subplugin https://github.com/jfederico/moodle-bbbext_b3dummy_override_view and make sure it is enabled:
git clone https://github.com/jfederico/moodle-bbbext_b3dummy_override_view mod/bigbluebuttonbn/extension/b3dummy_override_view
- Create a BigBlueButton activity in the course.
Testing the extensions can implement *_override_view
- Go to the course and access the BigBlueButton activity. The regular custom view is replaced by the extension View by override
- Go to the plugin management and disable the extension BigBlueButton B3Dummy for Override View and access the BigBlueButton activity. In the regular View is visible
Requirements A BigBlueButton server is setup: To set up the BBB server, you can register at https://registration-portal.blindsidenetworks.com/ to obtain credentials. Setup Login as admin. Go to Site administration > Plugins > Manage activities and enable the BigBlueButton plugin. Go to BBB settings and configure the BigBlueButton server URL and BigBlueButton shared secret. Go to Site administration > Plugins > BigBlueButton > Experimental Settings and enable Register live sessions (bigbluebuttonbn_meetingevents_enabled) Go to Site administration > Development > and enable DEBUG_DEVELOPER. Install the subplugin https://github.com/jfederico/moodle-bbbext_b3dummy_override_view and make sure it is enabled: git clone https: //github.com/jfederico/moodle-bbbext_b3dummy_override_view mod/bigbluebuttonbn/extension/b3dummy_override_view Create a BigBlueButton activity in the course. Testing the extensions can implement *_override_view Go to the course and access the BigBlueButton activity. The regular custom view is replaced by the extension View by override Go to the plugin management and disable the extension BigBlueButton B3Dummy for Override View and access the BigBlueButton activity. In the regular View is visible - A BigBlueButton server is setup:
-
Code verified against automated checks. 
Checked MDL-84903 using repository: https://github.com/jfederico/moodle
More information about this report
Built on: Wed Apr 16 19:37:58 UTC 2025
-
main (0 errors / 0 warnings) [branch: Problem Statement
Currently, the BigBlueButtonBN plugin lacks a standardized mechanism for extensions (subplugins) to modify or extend its view. This limitation restricts modular customization, preventing subplugins from adding their own UI elements or integrating seamlessly with the BigBlueButtonBN interface.
Proposed Solution
To improve flexibility and maintainability, we propose introducing a mechanism that allows subplugins to dynamically extend the BigBlueButtonBN view. This will enable better customization without requiring direct modifications to the core plugin.
Implementation Details
- Allow subplugins to override and extend specific sections of the BigBlueButtonBN view, ensuring modular customization.
- Provide a mechanism to define view extensions with precedence control, ensuring that only one extension takes priority when necessary.
- Enable multiple subplugins to inject UI elements without modifying core plugin files.
- Ensure backward compatibility by maintaining the existing rendering structure.
- Implement a standardized API for subplugins to register and manage view extensions.
Acceptance Criteria
- Introduce a structured way for subplugins to modify or extend the BigBlueButtonBN view.
- Ensure subplugins can add UI components without altering core plugin files.
- Maintain backward compatibility with existing view behavior.
- Implement Moodle-standard hooks or callback mechanisms to facilitate controlled extension.
- Provide documentation or examples demonstrating how subplugins can extend the BigBlueButtonBN view.
