New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement server-side login Jitsi Meet Polls #403
Comments
Big problems:
Up to now, in our production installation, there actually three "nonsense votings" lingering around from some users quick evaluation. How to get rid of them at all, maybe by an SQL statement? |
Solved by upgrading to V1.0.2 of the RawPropertyEditor-Plugin |
Observation: I found the poll data entries also at the special "focus" room. I delete them there and since this it seems that a client starts with an empty poll panel at least on a new room. |
The implementation of Polls by Jitsi is meant for temporary rooms that get deleted after everyone leaves the room. Using Polls with persistent rooms in Openfire will require additional logic to clean up polls that have expired and adding an owner value to identify who created it. This is additional work and should be a new issue. |
But for some reason the "three existing" polls appear at every room, even non-sticky new ones. This was reported by one of our users and verified by me. |
Unfortunately, I can't reproduce this. MUC Properties are cached by Openfire. You might want to reduce the expiry time otherwise, the next time a non-sticky room is used, the non-expired polls will be sent to each participant when they join. I have added additional code for making sure focus user is not sent polls data |
Thank you in advance. Unfortunately I had have no time yet to investigate how to actually produce the issue. Will report about later ... |
I extracted
|
Observation: Using the properties URL from history, e.g. |
It might make sense to delete the poll when the room is destroyed in Openfire |
This commit will remove all room polls when the room is destroyed. However, the data is cached and the poll will still be available if room is re-used before the cache expires |
Can't believe: The call of |
Port code from Lua to Java
See https://github.com/jitsi/jitsi-meet/blob/68eb0795eb6a87189e27001d2e95c701536dac3f/resources/prosody-plugins/mod_polls.lua
The text was updated successfully, but these errors were encountered: