The Elearning Community

Good day.

We've setup our own BigBlueButton server and successfully configured and tested it through the APIMate (https://mconf.github.io/api-mate/) testing links. Also enabled the Conference Big Blue Button plugin and configured it with the relevant server URL, Salt and port.

When trying to start a new Video Conference by clicking on the create link in the Collaborative Area I only get an HTTP 500 Error from the lms server. It does not seem to even go through to the BigBlueButton server.

I then tried to test with the BigBlueButton test server and get the exact same Error 500 response.

I'm running FormaLMS 2.3 on a hosted Google VM server.

Do you have any idea what the possible issue could be?

Check you apache error logs or activate debug in config.php and post the fatal error you will get.

Here is the error that I receive:

Fatal error: Cannot make static method FormaPlugin::getUrl() non static in class Plugin\ConferenceBBB\Conference in /var/www/html/plugins/ConferenceBBB/Conference.php on line 22

PHP version?

PHP 7.0.33-30+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Aug 7 2020 14:47:32) ( NTS )

https://forum.formalms.org/13/13986.html
https://forum.formalms.org/4/13608.html

It's a known bug. It must be fixed.

Is there a timeline?
Does it work in Forma Version 2.4?

This is critical for us as we have moved all our learners to distance learning with the ongoing COVID pandemic. External Webinar systems do not work well as it requires additional signup for the students...

No timeline I know man.
You can hire a developer to fix it on your instance.
If interested, you contact me as said in the other quoted topics.

alfa24 wrote: ↑Tue Aug 17, 2021 10:04 pm https://forum.formalms.org/13/13986.html
https://forum.formalms.org/4/13608.html

It's a known bug. It must be fixed.

Can you please point us to the bug? As far as I know the BBB integration works fine

Three users affected is enough to confirm it as a bug.
I didn't replicated it yet, but I think I know how to do. BBB plugin has not been tested enough in my instances because my customers use different solutions. I remember of similar bugs in other plugins, so that I needed to refactory the whole plugin system.