BigBlueButton BN

The only workaround I have right now for groups is to create multiple rooms within a course and specify in the activity title which group the room is for.

Thank you Jesus for addressing that so quickly.
There is another issue with both the 1.9 and 2.2 versions of the plugin in relation to groups.
Previous versions of big blue button allowed you to create groups within a course and then create one big blue button room with a specific group setting.
In 1.9 you have the options of no groups, visible groups and separate groups. If visible groups was selected, as a student, you could enter the room and choose the specific group's room (breakout room) you wanted to join from a drop down combo box. If you had two groups: Group A and Group B you had the option to join either room.
With separate groups you were autojoined to the room for your specific group.
As an administrator you always had the option to pick which room you wanted to join regardless of the setting.
In 2.2 you have the options of no groups and separate groups. Visible groups is no longer an options. That may be by design but that isn't the functionality problem I'm detailing here.
The groups feature is not working in either 1.9 or 2.2 regardless of whether you have separate groups or visible groups selected. When you attempt to enter the rooms there is a join button you have to press to join and that button is not working.
In 2.2 since you only allow separate groups this problem only affects administrative level users in the course who aren't a member of the groupings.
In 1.9 it affects students as well if an activity is set to visible groups.
You can replicate in one of three ways:
Moodle 1.9: Create a BBB activity and set it to visible or separate groups and attempt to join as an administrator.
Moodle 1.9: Create a BBB activity and set it to visible groups and attempt to join a room as a student within a group.
Moodle 2.2: Create a BBB activity and set it to separate groups and attempt to join a room as an administrator.

I have opened the issue https://tracker.moodle.org/browse/CONTRIB-4224. We'll follow-up this issue using the tracking system

Hi Daniel,
I just confirmed your report on 1.9.17. Could you please open an issue in the tracking system https://tracker.moodle.org/browse/CONTRIB/component/12231 This way we will be able to follow-up.
As I always say, that is the best place to report issues or ask for features. Problems are always best tracked in the forums.

There is also an active problem with the 1.9 version of this plugin. When you select the checkbox to open in a new window it results in a cache error.
"Could not cache module information for course"
This error occurs when the course is attempting to write out the modinfo field in the mdl_course table. There is an apparent problem with the code in the Big Blue Button module that is preventing this field from being written out.
We originally thought it might be an issue with the modinfo field or the datatype. We also increased the max_packet_size as suggested by other similar errors but that did not fix the issue.
I eventually stumbled upon the issue through messing around adding and removing big blue button rooms attempting to recreate the problem. I am now able to recreate this issue multiple times by just adding a big blue button room to any course and set it to open in a new window.
I am using the latest version for 1.9 : 1.0.9-b2 (2013030100)
Our workaround for right now is just to not set the rooms to open in a new window until it can be addressed.
We are using Moodle 1.9.10 and php version 5.3.2

Recording time, can not record a desktop sharing

Thanks, Jesus. I've created the issue here: https://tracker.moodle.org/browse/CONTRIB-4134

Thank you Shawn for letting us know. We'll take a look to this issue as soon as possible. In the mean while you could give us a hand creating the issue in the tracking system https://tracker.moodle.org/browse/CONTRIB/component/12231.
Regards
Jesus

FYI, I have this installed on Moodle 2.4 and opening the activity up in a new window is not working. I took a look at the code and didn't see any issues there. It seems that Moodle is stripping the 'target="_blank"' from the URL string.

Hi Rob,
This problem occurs when you Moodle server isn't able to make a direct connection to your BigBlueButton server (to make API calls).
Can you double-check that your Moodle server can make an HTTP request to your BigBlueButton server and try again.
The reason the demo works is that your Moodle Server is able to directly connect the test-install server.

We've installed the module in Moodle 2.2 and we get the "could not parse to XML" error as well when using the blindsidenetworks server and key and a "Unable to connect. Please check the url of the BigBlueButton server AND check to see if the BigBlueButton server is running" when using our own server. The demo worked on the server.

i installed the module in Moodle 2.4, but when adding the activity I get an error "could not parse to XML". I used the latest download version, how can I solve this?

Hi Dave, we don't have plans to add that functionality of uploading a default presentation, so if you want to take a shot at it - -go for it!

Is anyone working on integrating the ability to upload a default presentation from moodle module form. I started working on it today but figured I'd ask so I didn't have to recreate the wheel.

Gunnar, This problem has been reported previously by people who had their BigBlueButton server broken. The first test you should be sure to do is testing the plugin using the servers by default provided by Blindside Networks. if you do a quick call to http://test-install.blindsidenetworks.com/bigbluebutton/api you should receive an xml response.
If you need further help please go to the forums. Either opening an new thread at http://moodle.org/mod/forum/view.php?id=7797 or with a post on the corresponding one to the release you are experiencing problems. http://moodle.org/mod/forum/discuss.php?d=208959 It will be easier to follow up there.
Also, if you think you found a bug that can be reproduced please add an issue with more details on the tracking system http://tracker.moodle.org/browse/CONTRIB/component/12231