__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
## BigBlueButtonBN extension subplugins The plugins are made to extend existing BigBlueButtonBN behaviour. For now, we have two extensions points using as base classes that should be implemented. * action_url_addons: inherit this class and redefine the execute method so add new parameter when we send an action url to the BigBlueButton server. * mod_instance_helper : inherit this class so all methods will be called when we either add/delete/or update a module instance. The extension classes should be placed in your plugin with exactly the same name but in a different namespace for example * **\\bbbext_<YOUREXTENSION>\\bigbluebuttonbn\\mod_instance_helper** to extend hooks from the mod_instance_helper class. Some examples are provided in the tests/fixtures/simple folder.
| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| .gitignore | File | 2 B | 0777 |
|
| README.md | File | 785 B | 0777 |
|