-
Bug
-
Resolution: Not a bug
-
Minor
-
None
-
4.5
While working on MDL-82872, we came across an issue with Moodle Logs breaking after a BigBlueButton Event was registered.
There is a workaround in place to bypass the error, but the underlying problem seems still to be present.
How to reproduce:
- On a fresh installation of Moodle 4.5, enable DEVELOPER Debug messages and set Display debug messages to true.
- Enable BigBlueButton, register some free credentials and set them up to the Plugin.
- Create a Course and add a BigBlueButton Room to it.
- Disable the workaround placed as part of the referred patch.
Now, here is the tricky part. To disable the workaround placed in code, comment the lines 70 and 72 in classes/event/base. - Launch into the BBB session, you don't need to do anything, you can close the tab.
- Back into the BBB Room Activity, go to More -> Logs
The view will be either broken like thisĀ
Or show an error like this
Either way this is only the symptom. The issue seems to be in the way the event is generated and stored.
One of the findings was that there is a difference in the data stored in the 'other' column in the mdl_logstore_standard_log table. Where for some developers the data stored is null while for others there is some extra character stored.
The 'null' value is what is causing the problem.
Furthermore, while debugging the issue, we observed that null seems to be really a string and not an actual NULL value.
The integration team decided to proceed as this was not related to the patch itself, but we agreed on investigating further as it seems that a patch will be needed for all stable versions.
- Discovered while testing
-
MDL-82872 Extend meeting_events with subplugins
-
- Closed
-