Recordings error: String could not be parsed as XML

i tested your new fix on fresh WP server, not on my site.
on my production site i use old 1.4.0 plugin. to conect to my 1.1 bbb server.
with more then 300 recordings in the list, do not have any problem on my site.

Hello again,

I checked the newer version and it now returns some results. However, those were only for one of the rooms and they are 15 (they were supposed to be that many), so there is no pagination shown, if it was meant to be shown that is.
$listOfMeetings and $meetingIDs looked normal, so I went to BigBlueButton::getRecordingsArray that didn’t work for me.

I assigned various values to $pagesize to see if there was any difference and there was. My problem is that although there is a cron job that deletes recordings older than 3 months, there are values remaining in bigbluebutton and bigbluebutton_logs, so I have to go beyond the first 100 results to see more meetings. I’ll manually clear some old entries anyway to get results earlier. So, at a glance, it seems to work.

My question is how the paginated results and the pagination itself are supposed to work, since I seem to be getting the correct results with the right entry, but I can’t toggle between the pages.

Btw:
1. You have declared $listOfRecordings twice (not that it makes any difference)
2. The delete function works for me (no test-install though)

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

Thanks for your efforts and your time ??