Scalelite Playback Chat Problem

[UĞUR ÖZBEK]

Hello everyone,
I am experiencing an issue with the chat playback on my Scalelite
recording servers and would appreciate your help. I have BigBlueButton
3.0.18 servers, and when I view the playback directly on the BBB
servers, the chat messages display correctly with no formatting
problems.
However, when the same recordings are processed through Scalelite, I
see incorrect formatting in the chat panel during playback. Instead of
plain text messages, the chat displays HTML tags such as:

<p>est</p>
<p>test</p>

This issue occurs on two different Scalelite versions: Scalelite 1.6.5
and Scalelite 1.6.11
To help illustrate the problem, I have included: Screenshots of the
Scalelite /version API outputs for both v1.6.5 and v1.6.11.

The docker ps output from the Scalelite 1.6.11 server

A screenshot from a BBB 3.0.18 server where the chat displays correctly

A screenshot from the Scalelite 1.6.11 playback where the chat
formatting issue appears

The BBB 3.0.18 servers produce correct chat XML/JSON, so the problem
seems to appear only after the recording is imported and served
through Scalelite. Has anyone encountered this issue before? Is this
related to a change in how newer BBB versions generate chat events, or
is this a Scalelite playback-proxy / importer parsing issue? Any
guidance or suggestions would be greatly appreciated.

Thank you!

[UĞUR ÖZBEK]

Hi Everyone,

Bigbluebutton-dev groups answered my problem. The link below addresses the issue. 

https://github.com/bigbluebutton/bbb-playback/issues/329

I would like to outline the steps I took here. These steps are for Scalelite version 1.6.11 and bigbluebutton/bbb-playback-proxy: latest Docker image. 

After changing the directory to the docker-compose.yml file. 

docker compose down
docker compose pull
docker compose build --no-cache
docker compose up -d
After that I open my chat problem recording is resolved. 

PS: Is the problem is still same. because of your cookie. Try new page or incognito mode.

[anton.g...@blindsidenetworks.com]

Thank you for linking (and expanding) on the solution!