J Federico

Unfortunately there is no way to do that trough configuration.

I think your best shoot would be to translate the strings (they are hard-coded though).
Line 30 and 31. See:
https://github.com/jfederico/wordpress-plugin_bigbluebutton/blob/1.x/bigbluebutton-plugin.php#L31

Or you can try commenting the line that sets the welcome message so you welcome message will be the one your BBB server has by default.

Comment line 503 and 504 and replace them with $welcome = “”;

https://github.com/jfederico/wordpress-plugin_bigbluebutton/blob/1.x/bigbluebutton-plugin.php#L503

Same thing on lines 1030 and 1031

https://github.com/jfederico/wordpress-plugin_bigbluebutton/blob/1.x/bigbluebutton-plugin.php#L1030

Thanks for the report. I’ll make sure to include this as for being reviewed soon.

JF

Hi there,

Returning ‘some’ results is what it was expected. Meaning, it works again the same way it worked before.

The logic was not changed at all, only the way the request for getRecordings is performed.

The issue was, if you can remember, that the URL used for a single GET request was too long as it included too many meetingids. Nginx in BBB was not able to process it.

The solution is to paginate the request but not the view (That is something else I am not going no go through in this version). Meaning that if you have (or have had) 300 meetings that were set up for being recorded, instead of a massive request, the plugin will attempt to perform 12 making use of only 25 meetingids for each one of them.

You can increase the page size but I would not recommend to decrease it.

Again, no matter how many recordings you have in BBB, the response may be 1, 1000 or none,the issue is that the plugin is trying to get the recordings from all those meetings that may have at least 1.

For that matter what you may want to clean as well is the content in wp_bigbluebutton_logs.

Regarding to the quality of the code, duplication, style etc, man you don’t have idea how many times I have been tempted on applying refactoring to some pieces of the code, but I have to be strong and get focused on only fixing what is failing :).

The problem is that this particular version is no longer a priority. There is a new one in process (v2.0) you can find that code in the master branch of the GitHub repo and at the same time resources are limited.

https://github.com/blindside networks.com/wordpress-plugin_bigbluebutton/

But anyways, the current version is also there (branch 1.x). I can see you are also a developer, so feel free to send pull request to any of the two versions.

We have hundreds of contributors to the core project (BBB) but unfortunately just a few working on integration, so, feel free to join the team 🙂

Anyways, I’m glad the patch works as expected.

Thanks for your collaboration. Yours is the kind of participation that we really appreciate. Most people just post the feature requests or issue and disappear. In most cases they don’t even bother on give us feedback is the solution applied worked 🙂

Cheers

JF

Yeah, I miscalculated the result of explode. A last micro bug I introduced when extended the bigbluebutton_recordings to allow filtering by token.

It should be good now.

Hi there,

It is true, sorry about that. The feature is and has been in the roadmap since long long time ago, BUT it was implemented until version 2.0.

Nonetheless while working on another issue related to recordings I noticed the filter was not there, so I just completed the implementation

I have the update for the requested feature, but it has not been released yet. The latest version available is in the github repository?

https://github.com/blindsidenetworks/wordpress-plugin_bigbluebutton/archive/1.x.zip

But I need more of your help. Can you please give a try and let me know how it goes? If everything looks OK I’ll release this version during the week.

Cheers,

JF

Hi there,

Good news!, I have the fix for the issue you reported, but it has not been released yet. Can you give a try to the latest version available in the github repository?

https://github.com/blindsidenetworks/wordpress-plugin_bigbluebutton/archive/1.x.zip

I need more of your help. Can you try it out ant tell me if it works for you? If everything looks OK I’ll release this version during the week.

Cheers,

JF

That is super odd.

I did not get from the first post (until now) that you had two sites in the same server. One working and the other one not working. That is what makes things so weird. The only explanation that comes to my mind is is that your request is getting a bad XML. But your logs won’t show if that is the case.

It is faiing here

[error] 25231#0: *74365 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught exception ‘Exception’ with message ‘String could not be parsed as XML’ in /…/bigbluebutton/php/bbb_api.php:46

Which means that the problem is here

https://github.com/blindsidenetworks/wordpress-plugin_bigbluebutton/blob/1.x/php/bbb_api.php#L46

Which means that the parameter pased as $data is incorrect.

$response = new SimpleXMLElement($data);

I was telling you to print an error. In the line 44 you can add something like

error_log($data);

Take that and use an xml formatter like

https://www.freeformatter.com/xml-formatter.html

And see where is broken (if anything)

The other thing I was telling you to do is to print the getRecordingURL so you can do the query in a browser and even see what meeting ids are used in the query. There is definitely something wrong in your deployment and you are debugging the code right there.

That is what I would do anyways if I could reproduce it on my own.